Triple
T30680740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Asian Orogenic Belt |
E781044
|
entity |
| Predicate | closedOcean |
P54604
|
FINISHED |
| Object | Paleo-Asian Ocean |
—
|
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: Paleo-Asian Ocean | Statement: [Central Asian Orogenic Belt, closedOcean, Paleo-Asian Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedOcean Context triple: [Central Asian Orogenic Belt, closedOcean, Paleo-Asian Ocean]
-
A.
collisionClosedOcean
chosen
Indicates a tectonic collision event that has resulted in the complete closure of an ocean basin between converging plates.
-
B.
seaOf
Indicates a relationship where one entity is metaphorically or literally surrounded or filled by another like a vast sea, emphasizing overwhelming abundance or expansiveness.
-
C.
endSea
Indicates that something marks the boundary or termination point of a sea or sea area.
-
D.
oceanicPortion
Indicates that one entity is a part or segment of an ocean or oceanic area in relation to another entity.
-
E.
primarySea
Indicates that one entity is the main or principal sea associated with another entity (such as a place, route, or feature).
- 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_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 8:32 p.m.