Triple
T29035010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paleo-Tethys Ocean |
E737832
|
entity |
| Predicate | existedAlong |
P166290
|
FINISHED |
| Object | northern margin of Gondwana |
—
|
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: northern margin of Gondwana | Statement: [Paleo-Tethys Ocean, existedAlong, northern margin of Gondwana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existedAlong Context triple: [Paleo-Tethys Ocean, existedAlong, northern margin of Gondwana]
-
A.
existedAs
Indicates that one entity had the status, form, or identity of another entity during a certain time or context.
-
B.
existedUnder
Indicates that one entity existed within the authority, jurisdiction, or domain of another entity during a certain period.
-
C.
existedAfter
Indicates that one entity came into existence only after another entity already existed.
-
D.
existedUntil
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
-
E.
existsFrom
Indicates that an entity comes into existence or begins to be valid starting from a specified point in time or condition.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603be0cc8190ba34acec15092a98 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 9:57 a.m.