Triple
T10639960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pantodontidae |
E250693
|
entity |
| Predicate | finFunction |
P68285
|
FINISHED |
| Object | pectoral fins used for gliding and maneuvering at surface |
—
|
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: pectoral fins used for gliding and maneuvering at surface | Statement: [Pantodontidae, finFunction, pectoral fins used for gliding and maneuvering at surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finFunction Context triple: [Pantodontidae, finFunction, pectoral fins used for gliding and maneuvering at surface]
-
A.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
-
B.
functie
Indicates that one entity serves as a function, role, or operational purpose in relation to another entity.
-
C.
finStructure
Indicates a relationship where one entity specifies or characterizes the fin-related structural features or configuration of another entity.
-
D.
기능
chosen
Indicates that an entity has a particular function, role, or operational capability.
-
E.
finColor
Indicates the relationship specifying the color of an entity’s fin or fins.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfcbe5308190986bba438d19e852 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:04 p.m.