Triple
T26816135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tian Tan Buddha |
E675124
|
entity |
| Predicate | seatingPosture |
P55537
|
FINISHED |
| Object | seated |
—
|
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: seated | Statement: [Tian Tan Buddha, seatingPosture, seated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingPosture Context triple: [Tian Tan Buddha, seatingPosture, seated]
-
A.
hasSeatingPose
chosen
Indicates that an entity is in a seated posture or arrangement, specifying how it is positioned while sitting.
-
B.
positionDuringSitting
Indicates the spatial position or posture an entity has specifically while it is in a sitting state.
-
C.
seatingPosition
Indicates the relative location or arrangement of an entity’s seat with respect to other seats or a reference point in a seating layout.
-
D.
describesPosture
Indicates that one entity specifies or characterizes the bodily position or stance (posture) of another entity.
-
E.
seatingDirection
Indicates the orientation or facing direction in which an entity is seated relative to a reference point or object.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 4:52 a.m.