Triple
T9531625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balitoridae |
E229909
|
entity |
| Predicate | finPosition |
P37140
|
FINISHED |
| Object | pectoral fins modified for adhesion |
—
|
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 modified for adhesion | Statement: [Balitoridae, finPosition, pectoral fins modified for adhesion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finPosition Context triple: [Balitoridae, finPosition, pectoral fins modified for adhesion]
-
A.
finishPosition
Indicates the final rank or place an entity achieves in an ordered outcome, such as a race, competition, or sequence of results.
-
B.
finPlacement
chosen
Indicates the relative position or arrangement of a fin on an object or organism.
-
C.
focusPosition
Indicates the spatial or logical position at which attention, concentration, or processing is currently directed within a given context.
-
D.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
-
E.
endTimePosition
Indicates the temporal position or point in time at which an event, state, or interval comes to an end.
- 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98b408648190a04127c1d47fe7d2 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.