Triple
T9572155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemichthyidae |
E230948
|
entity |
| Predicate | jawFunction |
P89874
|
FINISHED |
| Object | used to sweep for small prey in the water column |
—
|
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: used to sweep for small prey in the water column | Statement: [Nemichthyidae, jawFunction, used to sweep for small prey in the water column]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jawFunction Context triple: [Nemichthyidae, jawFunction, used to sweep for small prey in the water column]
-
A.
jawType
Indicates the specific kind or classification of jaw structure associated with an entity.
-
B.
jawMechanics
Indicates the functional relationship between jaw structure and its movements or forces during actions like biting, chewing, or speaking.
-
C.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
-
D.
fromMouth
Indicates that something originates from or is emitted out of a mouth.
-
E.
wingFunction
Indicates the functional role or purpose that a wing serves in enabling certain actions or capabilities.
- F. None of above. chosen
Provenance (4 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998bf20881909fad48ecb16dfa31 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:04 p.m.