Triple
T24254138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas House |
E603617
|
entity |
| Predicate | architectDesigned |
P85898
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Douglas House, architectDesigned, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectDesigned Context triple: [Douglas House, architectDesigned, true]
-
A.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
B.
currentBuildingDesignedBy
Indicates that the building currently associated with an entity was designed by a specified architect or designer.
-
C.
architectOfStructure
chosen
Indicates that an entity is the designer or creator responsible for the architectural design of a particular structure.
-
D.
architecturalPlanner
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of another entity.
-
E.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b8bcb1c8190995e464a5f85fba9 |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.