Triple
T30489180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flaming June |
E775810
|
entity |
| Predicate | hasSubjectPose |
P196263
|
FINISHED |
| Object | reclining figure |
—
|
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: reclining figure | Statement: [Flaming June, hasSubjectPose, reclining figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectPose Context triple: [Flaming June, hasSubjectPose, reclining figure]
-
A.
hasSubjectPosition
Indicates that an entity occupies or is assigned to a particular subject role or position within a structure, context, or organization.
-
B.
hasBodyPosition
chosen
Indicates a relationship where an entity is associated with a specific physical posture or spatial orientation of its body.
-
C.
hasComponentPose
Indicates that an entity has a specific spatial pose (position and orientation) assigned to one of its components.
-
D.
hasSubjectMovement
Indicates that the subject of a clause has undergone syntactic movement from its original position to another position in the sentence structure.
-
E.
hasSeatingPose
Indicates that an entity is in a seated posture or arrangement, specifying how it is positioned while sitting.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 29, 2026, 8:13 p.m.