Triple
T36579462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pliohippus |
E902348
|
entity |
| Predicate | hasCommonDescription |
P204948
|
FINISHED |
| Object | three-toed Miocene horse |
—
|
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: three-toed Miocene horse | Statement: [Pliohippus, hasCommonDescription, three-toed Miocene horse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonDescription Context triple: [Pliohippus, hasCommonDescription, three-toed Miocene horse]
-
A.
hasDescription
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
B.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
C.
isCommonlyDefinedBy
Indicates that something is typically or most frequently characterized, specified, or described by a particular definition, property, or set of criteria.
-
D.
hasCommonTitle
Indicates that two or more entities share the same title or designation.
-
E.
hasCommonReference
Indicates that two or more entities share the same source, citation, or referential basis.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.