Triple
T26241613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Room 2 of the Temple of the Murals |
E656328
|
entity |
| Predicate | sequenceWithinTemple |
P51530
|
FINISHED |
| Object | second chamber of three in the Temple of the Murals |
—
|
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: second chamber of three in the Temple of the Murals | Statement: [Room 2 of the Temple of the Murals, sequenceWithinTemple, second chamber of three in the Temple of the Murals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceWithinTemple Context triple: [Room 2 of the Temple of the Murals, sequenceWithinTemple, second chamber of three in the Temple of the Murals]
-
A.
positionInTemple
chosen
Indicates the specific location or role an entity occupies within a temple.
-
B.
timeInTemple
Indicates the amount of time an entity spends or is present within a temple.
-
C.
hasStepsToTemple
Indicates that one place or structure includes or provides a set of steps leading to a temple.
-
D.
residesInTemple
Indicates that one entity lives or dwells within a temple associated with another entity.
-
E.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60d8f7f9c8190bb8cb8f8ac4c0ca5 |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:03 p.m.