Triple
T9506756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pannotia |
E229288
|
entity |
| Predicate | breakupContributedTo |
P35030
|
FINISHED |
| Object | opening of the Iapetus Ocean |
—
|
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: opening of the Iapetus Ocean | Statement: [Pannotia, breakupContributedTo, opening of the Iapetus Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakupContributedTo Context triple: [Pannotia, breakupContributedTo, opening of the Iapetus Ocean]
-
A.
breakupLinkedTo
chosen
Indicates a causal or associative relationship where a breakup is connected to, influenced by, or results from another event, factor, or entity.
-
B.
breakupProduced
Indicates that one entity was created or resulted from the breakup or disintegration of another entity.
-
C.
breaksUpWith
Indicates that one entity ends a romantic or intimate relationship with another entity.
-
D.
breakupDate
Indicates the date on which a romantic or partnership relationship between two entities ended.
-
E.
breakupProcess
Indicates the process by which a relationship or union between entities is dissolved, including the steps or phases leading to their separation.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98543b1881908b537abdc1d2f9c0 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.