Triple
T37817523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arcade Building (Pullman, Illinois) |
E942814
|
entity |
| Predicate | architectFor |
P6475
|
FINISHED |
| Object | Pullman Company |
—
|
NE NERFINISHED |
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: Pullman Company | Statement: [Arcade Building (Pullman, Illinois), architectFor, Pullman Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectFor Context triple: [Arcade Building (Pullman, Illinois), architectFor, Pullman Company]
-
A.
architectInstanceOf
Indicates that an architect is an instance or specific example of a more general architect class or type.
-
B.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
C.
architecturalRole
Indicates the functional or design-related role that one entity plays within the structure, layout, or organization of another entity.
-
D.
architecturalPlanner
chosen
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of another entity.
-
E.
possibleArchitect
Indicates that an entity is a candidate or likely creator/designer (architect) of another entity, but this authorship is not confirmed.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:19 p.m.