Triple
T21162409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Haul |
E521473
|
entity |
| Predicate | combinerLimbPosition |
P59595
|
FINISHED |
| Object | Lower torso of Devastator |
—
|
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: Lower torso of Devastator | Statement: [Long Haul, combinerLimbPosition, Lower torso of Devastator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinerLimbPosition Context triple: [Long Haul, combinerLimbPosition, Lower torso of Devastator]
-
A.
hasLimb
chosen
Indicates that an entity possesses a specific limb as part of its body.
-
B.
limbType
Indicates the specific kind or category of limb associated with an entity (e.g., arm, leg, wing, fin).
-
C.
isJointPosition
Indicates that an entity occupies or specifies a particular position or configuration within a joint (e.g., in a mechanical, robotic, or anatomical system).
-
D.
positionInArms
Indicates that one entity is being held or carried within the arms of another entity.
-
E.
limbCount
Indicates the number of limbs an entity possesses.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72532e9348190ad37fe858843d0f5 |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.