Triple
T30002090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niōmon gate |
E762195
|
entity |
| Predicate | guardianStatuesPosition |
P59806
|
FINISHED |
| Object | one on each side of the passage |
—
|
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: one on each side of the passage | Statement: [Niōmon gate, guardianStatuesPosition, one on each side of the passage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardianStatuesPosition Context triple: [Niōmon gate, guardianStatuesPosition, one on each side of the passage]
-
A.
guardianStatuesLocation
chosen
Indicates the location where guardian statues are situated or positioned.
-
B.
guardianStatuesType
Indicates that one entity is a type or category of guardian statues associated with another entity.
-
C.
guardianStatuesCount
Indicates the number of guardian statues associated with or present at a given entity or location.
-
D.
positionOfStatue
Indicates the spatial location where a statue is situated or placed.
-
E.
guardianShrineOf
Indicates a relationship where one entity serves as a protective or custodial shrine dedicated to 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 6:41 p.m.