Triple
T26738364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plesiosauria |
E674176
|
entity |
| Predicate | bodyPlanVariation |
P7383
|
FINISHED |
| Object | long-necked small-headed forms |
—
|
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-necked small-headed forms | Statement: [Plesiosauria, bodyPlanVariation, long-necked small-headed forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyPlanVariation Context triple: [Plesiosauria, bodyPlanVariation, long-necked small-headed forms]
-
A.
bodyPlan
chosen
Indicates the overall structural organization and arrangement of an organism’s body, including the layout and relationship of its major parts.
-
B.
designVariant
Indicates that one entity is an alternative design or version derived from or related to another entity’s design.
-
C.
bodyVariant
Indicates that one entity is an alternative physical form or version of another entity’s body.
-
D.
compositionVariesBy
Indicates that the composition of something differs depending on a specified factor, condition, or context.
-
E.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618469dc081908c9db3b9d1f5bb4c |
completed | May 2, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:48 a.m.