Triple
T20892923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lystrosaurus |
E514451
|
entity |
| Predicate | skullFeature |
P117695
|
FINISHED |
| Object | pair of tusks in 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: pair of tusks in upper jaw | Statement: [Lystrosaurus, skullFeature, pair of tusks in upper jaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skullFeature Context triple: [Lystrosaurus, skullFeature, pair of tusks in upper jaw]
-
A.
skullMorphology
chosen
Indicates a relationship where entities are characterized or compared based on the form, structure, or anatomical features of their skulls.
-
B.
skeletonFeature
Indicates that one entity is a structural or anatomical skeletal feature or component of another entity.
-
C.
skullUsage
Indicates how a skull is used, applied, or functionally involved in a particular context or activity.
-
D.
skullOrnamentation
Indicates that an entity has decorative or structural features specifically adorning or modifying the skull.
-
E.
hasSkull
Indicates that an entity possesses or is characterized by the presence of a skull.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05fecd88190905a0ea80a24406a |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.