Triple
T29692503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skull 5 |
E751247
|
entity |
| Predicate | hasBraincaseShape |
P160469
|
FINISHED |
| Object | long low braincase |
—
|
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: long low braincase | Statement: [Skull 5, hasBraincaseShape, long low braincase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBraincaseShape Context triple: [Skull 5, hasBraincaseShape, long low braincase]
-
A.
skullMorphology
Indicates a relationship where entities are characterized or compared based on the form, structure, or anatomical features of their skulls.
-
B.
hasSkullFeature
chosen
Indicates that an entity possesses a specific characteristic, structure, or attribute of the skull.
-
C.
hasEndoskeleton
Indicates that an entity possesses an internal supporting skeleton structure within its body.
-
D.
hasBrainToBodyRatio
Indicates the proportional relationship between the size or mass of an entity’s brain and the size or mass of its body.
-
E.
hasHingedPlastronOrCarapace
Indicates that an entity possesses a plastron or carapace that is hinged, allowing parts of the shell to move relative to each other.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 7:18 p.m.