Triple
T5383266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle skyline |
E113140
|
entity |
| Predicate | containsStructureFromEra |
P62926
|
FINISHED |
| Object | early 20th century (Smith Tower) |
—
|
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: early 20th century (Smith Tower) | Statement: [Seattle skyline, containsStructureFromEra, early 20th century (Smith Tower)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsStructureFromEra Context triple: [Seattle skyline, containsStructureFromEra, early 20th century (Smith Tower)]
-
A.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
B.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
C.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
D.
followsEra
Indicates that one time period or era comes directly after another in chronological order.
-
E.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
- F. None of above. chosen
Provenance (4 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd853005088190b1b092a9beb090b2 |
completed | March 20, 2026, 5:34 p.m. |
Created at: March 20, 2026, 2:03 p.m.