Triple
T34842825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of a Thousand Orifices |
E1004386
|
entity |
| Predicate | refersToBuildingCurrentName |
P147423
|
FINISHED |
| Object | Jardine House |
E306580
|
NE 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: Jardine House | Statement: [House of a Thousand Orifices, refersToBuildingCurrentName, Jardine House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToBuildingCurrentName Context triple: [House of a Thousand Orifices, refersToBuildingCurrentName, Jardine House]
-
A.
refersToBuildingOn
chosen
Indicates that one entity explicitly references or designates a specific building as its subject or target.
-
B.
buildingCurrentName
Indicates the name currently used to refer to a given building.
-
C.
currentBuilding
Indicates that an entity is located in, associated with, or belongs to the building that is relevant in the current context.
-
D.
originalBuildingName
Indicates that a building’s referenced name is its original or historically first assigned name, as opposed to any later or alternate names.
-
E.
mainBuildingName
Indicates the name that is designated as the primary or main building associated with an entity.
- F. None of above.
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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b2599c3c8190b7b9749e02184e7b |
completed | June 21, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4 p.m.