Triple
T10560675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exocoetidae |
E249208
|
entity |
| Predicate | finSpecialization |
P37269
|
FINISHED |
| Object | pectoral fins act as wings during gliding |
—
|
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 act as wings during gliding | Statement: [Exocoetidae, finSpecialization, pectoral fins act as wings during gliding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finSpecialization Context triple: [Exocoetidae, finSpecialization, pectoral fins act as wings during gliding]
-
A.
finPlacement
Indicates the relative position or arrangement of a fin on an object or organism.
-
B.
finStructure
chosen
Indicates a relationship where one entity specifies or characterizes the fin-related structural features or configuration of another entity.
-
C.
issuerSpecialization
Indicates the particular field, domain, or area of expertise in which the issuer is specialized.
-
D.
positionSpecialization
Indicates that one position is a more specialized or focused variant of another, broader position.
-
E.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5271f3c6c819080b49fbe3aa09e09 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.