Triple
T5805640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crocodilia |
E128737
|
entity |
| Predicate | jawMechanics |
P66622
|
FINISHED |
| Object | strong bite force |
—
|
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: strong bite force | Statement: [Crocodilia, jawMechanics, strong bite force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jawMechanics Context triple: [Crocodilia, jawMechanics, strong bite force]
-
A.
jawType
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.
neckJoint
Indicates a joint or connection located at or functioning as the neck between two body parts or structural elements.
-
D.
mouthNear
Indicates that one entity’s mouth is positioned close to another entity or object in space.
-
E.
mouthState
Indicates the current condition or configuration of an entity’s mouth, such as whether it is open, closed, or in another specific state.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1461a48190be2042dd3823d02e |
completed | March 22, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02b10def8819080859bc6505405ed |
completed | March 22, 2026, 5:46 p.m. |
Created at: March 22, 2026, 3:52 p.m.