Triple
T15120368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proboscidea |
E361154
|
entity |
| Predicate | diversificationPeak |
P116359
|
FINISHED |
| Object | Miocene |
—
|
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: Miocene | Statement: [Proboscidea, diversificationPeak, Miocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diversificationPeak Context triple: [Proboscidea, diversificationPeak, Miocene]
-
A.
peakDiversity
chosen
Indicates the point or condition at which diversity reaches its maximum level within a given context or system.
-
B.
diversifiedIn
Indicates that an entity has expanded its involvement, investments, or activities across multiple different areas, sectors, or asset types.
-
C.
sawDiversificationOf
Indicates that the subject experienced or witnessed a process in which something became more varied, diverse, or differentiated over time.
-
D.
peakType
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
E.
centralPeak
Indicates that one entity is the central, elevated peak located near the middle of another entity, typically within a larger structure such as a crater or basin.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059e036c8190959ff3bde8f2356f |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.