Triple
T2000567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodinia |
E43459
|
entity |
| Predicate | assemblyTimeInterval |
P35028
|
FINISHED |
| Object | 1.3–0.9 billion 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: 1.3–0.9 billion years ago | Statement: [Rodinia, assemblyTimeInterval, 1.3–0.9 billion years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assemblyTimeInterval Context triple: [Rodinia, assemblyTimeInterval, 1.3–0.9 billion years ago]
-
A.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
B.
dosingInterval
Indicates the time period that should elapse between consecutive doses of a medication or treatment.
-
C.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
D.
timeStructure
Indicates that one entity defines, constrains, or organizes the temporal framework or schedule within which another entity exists or operates.
-
E.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
- 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.