Triple
T4409088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Bailey area |
E94805
|
entity |
| Predicate | developmentBeganInPeriod |
P10779
|
FINISHED |
| Object | 2010s |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 2010s | Statement: [New Bailey area, developmentBeganInPeriod, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentBeganInPeriod Context triple: [New Bailey area, developmentBeganInPeriod, 2010s]
-
A.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
B.
developmentBegan
chosen
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
C.
developedOverPeriod
Indicates that something was created, expanded, or progressed continuously throughout a specified span of time.
-
D.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
E.
developedSince
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3548e24d08190a38c0bcd4b6ad571 |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.