Triple
T346155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurasian Plate |
E6945
|
entity |
| Predicate | isSeparatedFrom |
P1175
|
FINISHED |
| Object | North American Plate by the Mid-Atlantic Ridge |
—
|
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: North American Plate by the Mid-Atlantic Ridge | Statement: [Eurasian Plate, isSeparatedFrom, North American Plate by the Mid-Atlantic Ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeparatedFrom Context triple: [Eurasian Plate, isSeparatedFrom, North American Plate by the Mid-Atlantic Ridge]
-
A.
separates
chosen
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
B.
separatedFromOffice
Indicates that an individual has been removed or dismissed from holding a particular office or official position.
-
C.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
D.
isNotPartOf
Indicates that one entity does not belong to, is not contained within, and is not a component or member of another entity.
-
E.
separatedFromCubaBy
Indicates that one entity is divided or kept apart from Cuba by a specified physical or conceptual boundary.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb0240e88190bc70784772f5fa30 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.