Triple
T11288593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Late Miocene |
E267262
|
entity |
| Predicate | sawDiversificationOf |
P98313
|
FINISHED |
| Object | bovids |
—
|
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: bovids | Statement: [Late Miocene, sawDiversificationOf, bovids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawDiversificationOf Context triple: [Late Miocene, sawDiversificationOf, bovids]
-
A.
diversifiedIn
Indicates that an entity has expanded its involvement, investments, or activities across multiple different areas, sectors, or asset types.
-
B.
hasInternalDiversity
Indicates that an entity contains multiple distinct types, elements, or subgroups within itself, rather than being uniform or homogeneous.
-
C.
varietyOf
Indicates that one entity is a specific type, kind, or variant of another, more general entity.
-
D.
sometimesDividedInto
Indicates that an entity is on some occasions partitioned or separated into distinct parts, sections, or groups, but not always.
-
E.
hasDivergence
Indicates that there is a difference, deviation, or separation between two otherwise related entities, states, or paths.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e98875a08190b8509fe55e49d52d |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.