Triple
T11115222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemme-Carrosio section |
E262868
|
entity |
| Predicate | markerEvent |
P92262
|
FINISHED |
| Object | base of the Miocene GSSP |
—
|
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: base of the Miocene GSSP | Statement: [Lemme-Carrosio section, markerEvent, base of the Miocene GSSP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: markerEvent Context triple: [Lemme-Carrosio section, markerEvent, base of the Miocene GSSP]
-
A.
anchorEvent
chosen
Indicates that one event serves as a fixed reference point in time or context for another event or set of events.
-
B.
marksMeetingPointOf
Indicates that something designates or identifies the specific location where two or more entities meet or converge.
-
C.
peakEvent
Indicates the occurrence of a maximum or most intense point within a process, activity, or measurable phenomenon.
-
D.
marksOccasion
Indicates that an event, action, or item serves to commemorate, celebrate, or formally recognize a particular occasion or milestone.
-
E.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa7254c8190abce35696ad2be03 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.