Triple
T5457356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooper-Lecky Architects |
E122511
|
entity |
| Predicate | designedStructureType |
P64156
|
FINISHED |
| Object | war memorial |
—
|
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: war memorial | Statement: [Cooper-Lecky Architects, designedStructureType, war memorial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedStructureType Context triple: [Cooper-Lecky Architects, designedStructureType, war memorial]
-
A.
designedStructureIn
Indicates that one entity is the designer or creator of a structure that is located within or associated with another specified entity or context.
-
B.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
C.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
D.
integratedStructure
Indicates that multiple components are combined into a single, cohesive structure that functions as an integrated whole.
-
E.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
- F. None of above. chosen
Provenance (4 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd927b0b4c81909d5e0f594822e3f9 |
completed | March 20, 2026, 6:31 p.m. |
Created at: March 20, 2026, 2:08 p.m.