Triple
T8468613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meishan section |
E200225
|
entity |
| Predicate | hasEventRecorded |
P22468
|
FINISHED |
| Object | largest known Phanerozoic mass extinction |
—
|
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: largest known Phanerozoic mass extinction | Statement: [Meishan section, hasEventRecorded, largest known Phanerozoic mass extinction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventRecorded Context triple: [Meishan section, hasEventRecorded, largest known Phanerozoic mass extinction]
-
A.
hasCoveredEvent
Indicates that one entity has reported on, documented, or provided coverage of a particular event.
-
B.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
C.
hadListeningEventAt
Indicates that a listening event involving an entity occurred at a specific time or place.
-
D.
hasLaunchHistoryEvent
Indicates that there exists a recorded event in the launch history associated with the given entity.
-
E.
hadEvent
chosen
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d445f48190884df64bb1aebd41 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.