Triple
T16553866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lafayette Towers Apartments East |
E402140
|
entity |
| Predicate | hasConstructionEra |
P22153
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Lafayette Towers Apartments East, hasConstructionEra, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstructionEra Context triple: [Lafayette Towers Apartments East, hasConstructionEra, mid-20th century]
-
A.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
B.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
C.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
D.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
E.
usedDuringEraOf
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc737ac8190b755e2a39b6ef32b |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.