Triple
T36761964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anapji Pond |
E908224
|
entity |
| Predicate | locatedInPalaceComplex |
P112021
|
FINISHED |
| Object | Donggung Palace |
E2011763
|
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: Donggung Palace | Statement: [Anapji Pond, locatedInPalaceComplex, Donggung Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPalaceComplex Context triple: [Anapji Pond, locatedInPalaceComplex, Donggung Palace]
-
A.
locatedInPalaceSection
Indicates that one entity is situated within a specific section or area of a palace.
-
B.
palaceLocatedIn
Indicates that a palace is situated within or belongs to a specific geographic or administrative location.
-
C.
housedWithinComplex
chosen
Indicates that one entity is located inside and functionally part of a larger building or facility complex.
-
D.
positionInForbiddenCity
Indicates a spatial or locational relationship where an entity is situated at or within a specific place or position inside the Forbidden City.
-
E.
partOfDynasticComplex
Indicates that one entity is a constituent element or subdivision within a larger dynastic complex or ruling lineage structure.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3c174280c48190ba89cdcb70e443b6 |
completed | June 24, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.