Triple
T1758857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Jurassic |
E38609
|
entity |
| Predicate | beganAfter |
P6880
|
FINISHED |
| Object | end-Triassic 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: end-Triassic mass extinction | Statement: [Early Jurassic, beganAfter, end-Triassic mass extinction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganAfter Context triple: [Early Jurassic, beganAfter, end-Triassic mass extinction]
-
A.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
B.
chronologicallyAfter
chosen
Indicates that one event or state occurs later in time than another.
-
C.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
D.
beganWith
Indicates that one event, process, or state started with or was initiated by another specified event, process, or state.
-
E.
createdBefore
Indicates that one entity was created at an earlier time than another entity.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.