Triple
T3787843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy of Holies |
E85570
|
entity |
| Predicate | positionInTemple |
P51530
|
FINISHED |
| Object | innermost chamber |
—
|
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: innermost chamber | Statement: [Holy of Holies, positionInTemple, innermost chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTemple Context triple: [Holy of Holies, positionInTemple, innermost chamber]
-
A.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
B.
positionInForbiddenCity
Indicates a spatial or locational relationship where an entity is situated at or within a specific place or position inside the Forbidden City.
-
C.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
D.
positionWithinForbiddenCity
Indicates that an entity’s location lies inside the spatial boundaries of the Forbidden City.
-
E.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
- F. None of above. chosen
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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
| PDg | Predicate description generation | batch_69aee633dab88190b14cec8afb19ca6a |
completed | March 9, 2026, 3:24 p.m. |
Created at: March 9, 2026, 3:13 p.m.