Triple
T33392245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cryptacanthodidae |
E855076
|
entity |
| Predicate | jawOrientation |
P77777
|
FINISHED |
| Object | oblique mouth |
—
|
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: oblique mouth | Statement: [Cryptacanthodidae, jawOrientation, oblique mouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jawOrientation Context triple: [Cryptacanthodidae, jawOrientation, oblique mouth]
-
A.
jawType
Indicates the specific kind or classification of jaw structure associated with an entity.
-
B.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
-
C.
jawFunction
Indicates the functional role, movement, or mechanical action performed by a jaw in relation to other anatomical structures or processes.
-
D.
mouthDirection
chosen
Indicates the orientation or facing direction of a mouth relative to a reference frame or another object.
-
E.
hasJaw
Indicates that one entity possesses or is equipped with a jaw as a physical anatomical feature.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:35 a.m.