Triple
T2361333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetraodontiformes |
E47277
|
entity |
| Predicate | jawCharacteristic |
P35419
|
FINISHED |
| Object | beak-like jaws in many species |
—
|
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: beak-like jaws in many species | Statement: [Tetraodontiformes, jawCharacteristic, beak-like jaws in many species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jawCharacteristic Context triple: [Tetraodontiformes, jawCharacteristic, beak-like jaws in many species]
-
A.
jawType
chosen
Indicates the specific kind or classification of jaw structure associated with an entity.
-
B.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
-
C.
mouthNear
Indicates that one entity’s mouth is positioned close to another entity or object in space.
-
D.
mouthState
Indicates the current condition or configuration of an entity’s mouth, such as whether it is open, closed, or in another specific state.
-
E.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc723c66481908a9b94991f651b3b |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.