Triple
T33989273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euleptorhamphus |
E871498
|
entity |
| Predicate | jawAsymmetry |
P177793
|
FINISHED |
| Object | lower jaw longer than upper jaw |
—
|
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: lower jaw longer than upper jaw | Statement: [Euleptorhamphus, jawAsymmetry, lower jaw longer than upper jaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jawAsymmetry Context triple: [Euleptorhamphus, jawAsymmetry, lower jaw longer than upper jaw]
-
A.
jawType
Indicates the specific kind or classification of jaw structure associated with an entity.
-
B.
jawFunction
Indicates the functional role, movement, or mechanical action performed by a jaw in relation to other anatomical structures or processes.
-
C.
hasJaw
Indicates that one entity possesses or is equipped with a jaw as a physical anatomical feature.
-
D.
jawMechanics
Indicates the functional relationship between jaw structure and its movements or forces during actions like biting, chewing, or speaking.
-
E.
jawEvolution
Indicates how the structure, function, or complexity of jaws has changed over evolutionary time within or across lineages.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70391008c81908b6fb826edb7cef4 |
completed | May 3, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f70101ba1c819099380274e6df9a4d |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7017e9aec819095465a53bb871a84 |
completed | May 3, 2026, 8:04 a.m. |
Created at: May 1, 2026, 1:50 a.m.