Triple
T14149607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth’s outer radiation belt |
E350639
|
entity |
| Predicate | isSeparatedBy |
P11855
|
FINISHED |
| Object | slot region |
—
|
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: slot region | Statement: [Earth’s outer radiation belt, isSeparatedBy, slot region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeparatedBy Context triple: [Earth’s outer radiation belt, isSeparatedBy, slot region]
-
A.
separatesBy
Indicates that one entity divides, partitions, or creates a boundary between two or more other entities.
-
B.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
C.
hasSeparator
chosen
Indicates that one entity includes, uses, or is divided by another entity that serves as a separator or delimiting element.
-
D.
isDividedFrom
Indicates that one entity is separated or partitioned from another, typically by a boundary, barrier, or dividing line.
-
E.
providesSeparationFor
Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61237ef481909374c1f68a2370b7 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:55 a.m.