Triple
T31038007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syndyoceras |
E790902
|
entity |
| Predicate | hornMorphology |
P161608
|
FINISHED |
| Object | paired horn cores on the 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: paired horn cores on the snout | Statement: [Syndyoceras, hornMorphology, paired horn cores on the snout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hornMorphology Context triple: [Syndyoceras, hornMorphology, paired horn cores on the snout]
-
A.
notableMorphology
Indicates that an entity is characterized by a distinctive or noteworthy physical form, structure, or shape.
-
B.
morphologicalEvidence
Indicates that there is supporting evidence based on the form, structure, or morphology of the entities involved.
-
C.
morphologicalInterpretation
Indicates the specific morphological analysis or grammatical form assigned to an element (such as a word or morpheme) within a linguistic structure.
-
D.
trapMorphology
Indicates the structural form or physical configuration of a trap in relation to the entity it belongs to.
-
E.
morphologicalTraits
chosen
Indicates a relationship where specific physical form or structural characteristics are attributed to or associated with an entity.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694f800e48190bad9640e6896b76b |
completed | May 3, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.