Triple
T31487932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namaqua-Natal orogeny |
E803328
|
entity |
| Predicate | continentDuringEvent |
P28160
|
FINISHED |
| Object | Rodinia |
—
|
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: Rodinia | Statement: [Namaqua-Natal orogeny, continentDuringEvent, Rodinia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentDuringEvent Context triple: [Namaqua-Natal orogeny, continentDuringEvent, Rodinia]
-
A.
continentInvolved
chosen
Indicates that a particular continent participates in, is affected by, or plays a role in a specified event, process, or relationship.
-
B.
continentOfActivity
Indicates the continent on which an entity primarily operates, is active, or conducts its main activities.
-
C.
continent
Indicates that one entity is a continent on which the other entity is geographically located or to which it belongs.
-
D.
continentReference
Indicates that one entity serves as a reference or pointer to a specific continent associated with another entity.
-
E.
continentFound
Indicates that a specified continent is the location where a particular entity is found or 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 30, 2026, 9:36 p.m.