Triple
T2000553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodinia |
E43459
|
entity |
| Predicate | brokeUpApproximately |
P3878
|
FINISHED |
| Object | 900 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 million years ago | Statement: [Rodinia, brokeUpApproximately, 900 million years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokeUpApproximately Context triple: [Rodinia, brokeUpApproximately, 900 million years ago]
-
A.
reentryBreakupDate
Indicates the date on which an object breaks apart during its reentry into an atmosphere.
-
B.
spouseRelationshipEnd
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
C.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
D.
separationYear
chosen
Indicates the year in which two entities ended or dissolved their relationship or association.
-
E.
timeAfterLiftoffAtBreakup
Indicates the elapsed time since liftoff at the moment when a breakup event (such as vehicle disintegration or structural failure) occurs.
- 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_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. |
Created at: March 4, 2026, 7:37 p.m.