Triple
T32545664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farallon–North American plate boundary |
E831841
|
entity |
| Predicate | largelyTerminated |
P174912
|
FINISHED |
| Object | Cenozoic Era |
—
|
NE NERFINISHED |
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: Cenozoic Era | Statement: [Farallon–North American plate boundary, largelyTerminated, Cenozoic Era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largelyTerminated Context triple: [Farallon–North American plate boundary, largelyTerminated, Cenozoic Era]
-
A.
typicallyTerminatedIn
Indicates that an event, process, or state usually ends or concludes in a particular way or outcome.
-
B.
wasTerminated
Indicates that an entity’s employment, contract, or ongoing role was ended, typically by a decision from another party rather than by the entity itself.
-
C.
natureOfTermination
Indicates the manner, cause, or conditions under which a relationship, contract, or employment is brought to an end.
-
D.
largelyRepealed
Indicates that most provisions or effects of one legal or formal rule have been officially revoked or annulled by another authority or rule.
-
E.
terminationEndedIn
Indicates that a termination event concluded with a specific outcome or result.
- F. None of above. chosen
Provenance (4 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: May 1, 2026, 1:02 a.m.