Triple
T2000568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodinia |
E43459
|
entity |
| Predicate | breakupTimeInterval |
P35029
|
FINISHED |
| Object | 900–700 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: 900–700 million years ago | Statement: [Rodinia, breakupTimeInterval, 900–700 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakupTimeInterval Context triple: [Rodinia, breakupTimeInterval, 900–700 million years ago]
-
A.
timeAfterLiftoffAtBreakup
Indicates the elapsed time since liftoff at the moment when a breakup event (such as vehicle disintegration or structural failure) occurs.
-
B.
reentryBreakupDate
Indicates the date on which an object breaks apart during its reentry into an atmosphere.
-
C.
interruptionDuration
Indicates the length of time for which an ongoing activity, process, or state is temporarily halted or disrupted.
-
D.
timeBetweenAnnouncementAndTermination
Indicates the duration of time that elapses between when something is officially announced and when it is subsequently terminated.
-
E.
durationUntil
Indicates the length of time remaining from a given starting point until a specified future event or state occurs.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb87f78f0819098e787a5f3e062fd |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb87b9fc08190a748c278ef2d7dc7 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:37 p.m.