Triple
T8468527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pangaea |
E200224
|
entity |
| Predicate | beganBreakingApartApproximately |
P19545
|
FINISHED |
| Object | 200 million years ago |
—
|
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: 200 million years ago | Statement: [Pangaea, beganBreakingApartApproximately, 200 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganBreakingApartApproximately Context triple: [Pangaea, beganBreakingApartApproximately, 200 million years ago]
-
A.
breaksUpIn
Indicates that one entity ends or dissolves a relationship or partnership with another entity.
-
B.
brokenUpAt
Indicates that a romantic or close relationship between two entities ended at a specific time or date.
-
C.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
D.
began
chosen
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
E.
brokenUp
Indicates that a previously existing romantic or close relationship between two entities has ended.
- 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.