Triple
T8200464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger Plateau |
E191556
|
entity |
| Predicate | separationProcess |
P81466
|
FINISHED |
| Object | continental rifting |
—
|
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: continental rifting | Statement: [Challenger Plateau, separationProcess, continental rifting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separationProcess Context triple: [Challenger Plateau, separationProcess, continental rifting]
-
A.
separationMethod
Indicates the technique or process used to separate one substance, component, or entity from another.
-
B.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
C.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
-
D.
separatesState
Indicates that one entity serves as a dividing boundary or barrier between two distinct states or regions.
-
E.
separationInterface
Indicates a boundary or medium through which two distinct entities are separated or kept apart.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df565dc819099537fc06b694b40 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb46635424819085d086972b264280 |
completed | March 31, 2026, 3:58 a.m. |
Created at: March 30, 2026, 5:43 p.m.