Triple
T3847316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall of Dispelling Clouds |
E85201
|
entity |
| Predicate | locatedInComplexType |
P36917
|
FINISHED |
| Object | imperial garden |
—
|
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: imperial garden | Statement: [Hall of Dispelling Clouds, locatedInComplexType, imperial garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInComplexType Context triple: [Hall of Dispelling Clouds, locatedInComplexType, imperial garden]
-
A.
positionWithinComplex
chosen
Indicates that one entity is located inside or forms a component part of a larger complex or compound structure.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
D.
belongsToBuildingComplex
Indicates that one building or structure is part of, or included within, a larger building complex.
-
E.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcb069881909d3536b18b7802a7 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.