Triple
T34842823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of a Thousand Orifices |
E1004386
|
entity |
| Predicate | refersToBuildingArchitect |
P49396
|
FINISHED |
| Object | Palmer & Turner |
—
|
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: Palmer & Turner | Statement: [House of a Thousand Orifices, refersToBuildingArchitect, Palmer & Turner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToBuildingArchitect Context triple: [House of a Thousand Orifices, refersToBuildingArchitect, Palmer & Turner]
-
A.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
B.
refersToBuildingOn
Indicates that one entity explicitly references or designates a specific building as its subject or target.
-
C.
hasRelationToArchitect
Indicates that one entity has a specified relationship or association with an architect.
-
D.
isArchitectDesigned
Indicates that something was created or planned by a professional architect.
-
E.
architectOfNewBuilding
chosen
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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 3, 2026, 4 p.m.