Triple
T8298946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurel District |
E194295
|
entity |
| Predicate | hasArchitectureEra |
P62926
|
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: [Laurel District, hasArchitectureEra, early 20th century commercial buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitectureEra Context triple: [Laurel District, hasArchitectureEra, early 20th century commercial buildings]
-
A.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
B.
hasPrimaryEra
Indicates that an entity is chiefly associated with or belongs to a particular historical or temporal era.
-
C.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
D.
containsStructureFromEra
chosen
Indicates that one entity includes or incorporates a structure that originates from a particular historical era.
-
E.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7dfb60e48190bfa5de1c1496d3b5 |
completed | March 31, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.