Triple
T7677442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GABI |
E173896
|
entity |
| Predicate | beganAround |
P2559
|
FINISHED |
| Object | late Miocene to Pliocene |
—
|
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: late Miocene to Pliocene | Statement: [GABI, beganAround, late Miocene to Pliocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganAround Context triple: [GABI, beganAround, late Miocene to Pliocene]
-
A.
began
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
B.
createdAround
Indicates that something was brought into existence or produced approximately at a particular time or within an imprecise time period.
-
C.
beganWith
Indicates that one event, process, or state started with or was initiated by another specified event, process, or state.
-
D.
emergedAround
chosen
Indicates that something came into existence or became noticeable at approximately a particular time or period.
-
E.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.