Triple
T22377640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spinario |
E553189
|
entity |
| Predicate | sittingPosture |
P55537
|
FINISHED |
| Object | seated with one leg crossed over the other |
—
|
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 with one leg crossed over the other | Statement: [Spinario, sittingPosture, seated with one leg crossed over the other]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sittingPosture Context triple: [Spinario, sittingPosture, seated with one leg crossed over the other]
-
A.
positionDuringSitting
Indicates the spatial position or posture an entity has specifically while it is in a sitting state.
-
B.
describesPosture
Indicates that one entity specifies or characterizes the bodily position or stance (posture) of another entity.
-
C.
hasSeatingPose
chosen
Indicates that an entity is in a seated posture or arrangement, specifying how it is positioned while sitting.
-
D.
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.
-
E.
cannotSit
Indicates that an entity is unable or not allowed to sit on, in, or at 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158292d80819094f474c0e9e14caf |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.