Triple
T321240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Actinopterygii |
E6419
|
entity |
| Predicate | hasBodyPlan |
P7383
|
FINISHED |
| Object | streamlined body common |
—
|
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: streamlined body common | Statement: [Actinopterygii, hasBodyPlan, streamlined body common]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyPlan Context triple: [Actinopterygii, hasBodyPlan, streamlined body common]
-
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.
definesBody
Indicates that one entity specifies or determines the physical structure, form, or composition of another entity’s body.
-
C.
hasDevolvedBody
Indicates that authority, responsibility, or powers have been transferred from a central entity to a subordinate or regional entity.
-
D.
establishesBodyType
Indicates that an entity defines or sets the physical or structural body type of another entity.
-
E.
supportsBody
Indicates that one entity physically or structurally holds up, bears the weight of, or provides foundational stability for another entity’s body.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e946607081909c8b97473aaf8d1b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.