Triple
T30680738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Asian Orogenic Belt |
E781044
|
entity |
| Predicate | formationBegan |
P654
|
FINISHED |
| Object | Neoproterozoic 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: Neoproterozoic era | Statement: [Central Asian Orogenic Belt, formationBegan, Neoproterozoic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formationBegan Context triple: [Central Asian Orogenic Belt, formationBegan, Neoproterozoic era]
-
A.
formationEvent
chosen
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
B.
instructionBegan
Indicates that an instructional process or teaching activity has started.
-
C.
useBegan
Indicates that an entity initiated or started using another entity or resource at a particular point in time.
-
D.
formationEntered
Indicates that an entity has moved into and assumed a specified formation relative to other entities.
-
E.
startedNear
Indicates that one event or action began close in time or space to another event or action.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 8:32 p.m.