Triple
T10123377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iapetus Ocean |
E223351
|
entity |
| Predicate | openedBetween |
P92107
|
FINISHED |
| Object | Laurentia and Baltica |
—
|
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: Laurentia and Baltica | Statement: [Iapetus Ocean, openedBetween, Laurentia and Baltica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedBetween Context triple: [Iapetus Ocean, openedBetween, Laurentia and Baltica]
-
A.
openedDuring
Indicates that an entity began operating, became accessible, or was inaugurated within a specified time period or event.
-
B.
openedForEvent
Indicates that a venue or location is made accessible and operational specifically for a particular event.
-
C.
serviceOpenedBetween
Indicates that a service has been initiated or made available during the time interval between two specified points or events.
-
D.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
opened
Indicates that one entity caused another entity (such as an object, container, or passage) to change from a closed or inaccessible state to an open or accessible state.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2ea7fe88190acb08d292a794638 |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:05 p.m.