Triple
T4411305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balistidae |
E94858
|
entity |
| Predicate | finArrangement |
P37269
|
FINISHED |
| Object | dorsal and anal fins used for precise maneuvering |
—
|
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: dorsal and anal fins used for precise maneuvering | Statement: [Balistidae, finArrangement, dorsal and anal fins used for precise maneuvering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finArrangement Context triple: [Balistidae, finArrangement, dorsal and anal fins used for precise maneuvering]
-
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.
finStructure
chosen
Indicates a relationship where one entity specifies or characterizes the fin-related structural features or configuration of another entity.
-
C.
finPlacement
Indicates the relative position or arrangement of a fin on an object or organism.
-
D.
chargeArrangement
Indicates an agreement or setup specifying how charges, fees, or payments are to be applied or managed between parties.
-
E.
arrangement
Indicates a relationship where entities are organized, ordered, or positioned in a particular configuration or sequence relative to one another.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e656dc819093ca8395d7334006 |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.