Triple
T22164826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadway (Galveston) |
E547763
|
entity |
| Predicate | hasBuildingEraAlong |
P93743
|
FINISHED |
| Object | late 19th 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: late 19th century | Statement: [Broadway (Galveston), hasBuildingEraAlong, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingEraAlong Context triple: [Broadway (Galveston), hasBuildingEraAlong, late 19th century]
-
A.
containsBuildingFromCentury
chosen
Indicates that a location or area includes at least one building that originates from a specified century.
-
B.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
C.
hasEraInfluence
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
-
D.
hasHistoricalEmpire
Indicates that an entity once possessed, controlled, or was associated with a significant imperial power in the past.
-
E.
historicalEraOfRise
Indicates the historical era or period during which an entity first rose to prominence, influence, or significance.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a309d8081908f4540fe2da63010 |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.