Triple
T36216628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Century Association |
E1047713
|
entity |
| Predicate | architectOfClubhouse |
P69997
|
FINISHED |
| Object | McKim, Mead & White |
—
|
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: McKim, Mead & White | Statement: [Century Association, architectOfClubhouse, McKim, Mead & White]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectOfClubhouse Context triple: [Century Association, architectOfClubhouse, McKim, Mead & White]
-
A.
hasClubhouseArchitect
chosen
Indicates that an entity’s clubhouse was designed or planned by a specified architect.
-
B.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
C.
architectOfStructure
Indicates that an entity is the designer or creator responsible for the architectural design of a particular structure.
-
D.
architectOfResidence
Indicates that one entity is the architect responsible for designing the residence associated with another entity.
-
E.
architectOfNewBuilding
Indicates that one entity is the architect responsible for designing a particular new building.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:09 p.m.