Triple
T4601072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ennis |
E100318
|
entity |
| Predicate | historicDowntownFeature |
P295
|
FINISHED |
| Object | early 20th-century commercial buildings |
—
|
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 commercial buildings | Statement: [Ennis, historicDowntownFeature, early 20th-century commercial buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicDowntownFeature Context triple: [Ennis, historicDowntownFeature, early 20th-century commercial buildings]
-
A.
capitalHistoric
Indicates that a location has served as a capital city at some point in history, even if it is not the current capital.
-
B.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
C.
historicLocationType
Indicates the specific kind or category of a place based on its historical significance or role.
-
D.
isHistoricPlace
Indicates that a place holds recognized historical significance, often due to its age, events, or cultural importance.
-
E.
hasHistoricDistrict
chosen
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd597346a08190b47eda3b73076f8b |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.