Triple
T3016215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skullcrawlers |
E82341
|
entity |
| Predicate | anatomicalFeature |
P45022
|
FINISHED |
| Object | elongated body |
—
|
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: elongated body | Statement: [Skullcrawlers, anatomicalFeature, elongated body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anatomicalFeature Context triple: [Skullcrawlers, anatomicalFeature, elongated body]
-
A.
embryologicalFeature
Indicates a relationship where one entity is an anatomical or biological structure characterized or defined by its origin, development, or properties during the embryonic stage.
-
B.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
C.
limbMorphology
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
D.
skeletonFeature
Indicates that one entity is a structural or anatomical skeletal feature or component of another entity.
-
E.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
- F. None of above. chosen
Provenance (4 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a6c56708190b7d8d08bca727cc1 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3 p.m.