Triple
T14149592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth’s outer radiation belt |
E350639
|
entity |
| Predicate | isDiscoveredIn |
P3986
|
FINISHED |
| Object | 1958 |
—
|
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: 1958 | Statement: [Earth’s outer radiation belt, isDiscoveredIn, 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDiscoveredIn Context triple: [Earth’s outer radiation belt, isDiscoveredIn, 1958]
-
A.
wasDiscoveredIn
chosen
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
B.
discoveredInCountry
Indicates that something was discovered within the geographical boundaries or jurisdiction of a specified country.
-
C.
discoveredAsPartOf
Indicates that something was found, identified, or revealed in the course of a larger activity, process, or investigation of which it formed a component.
-
D.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
E.
countryOfExploration
Indicates the country under whose auspices or within whose territory an exploration activity was conducted.
- 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.