Triple
T15239441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champsosaurus |
E364214
|
entity |
| Predicate | nostrilPlacement |
P117696
|
FINISHED |
| Object | terminal or near-terminal nares on snout |
—
|
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: terminal or near-terminal nares on snout | Statement: [Champsosaurus, nostrilPlacement, terminal or near-terminal nares on snout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nostrilPlacement Context triple: [Champsosaurus, nostrilPlacement, terminal or near-terminal nares on snout]
-
A.
nostrilOrientation
Indicates the directional alignment or facing angle of an entity’s nostrils relative to a reference frame or axis.
-
B.
noseType
Indicates the specific shape or classification of a nose that an entity possesses.
-
C.
noseLength
Indicates the length or size of an entity’s nose, typically as a measurable physical attribute.
-
D.
noseleaf
Indicates that an entity possesses or is characterized by a specialized leaf-like structure on or around the nose, typically associated with certain animals (such as bats).
-
E.
fromNoseCame
Indicates that something originated from or was expelled out of a nose.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007db9a148190aadea8d5f8b6b261 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:12 a.m.