Triple
T229450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Hemisphere |
E4378
|
entity |
| Predicate | coordinateRange |
P4679
|
FINISHED |
| Object | 0°E to 180°E longitude (conventional) |
—
|
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: 0°E to 180°E longitude (conventional) | Statement: [Eastern Hemisphere, coordinateRange, 0°E to 180°E longitude (conventional)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateRange Context triple: [Eastern Hemisphere, coordinateRange, 0°E to 180°E longitude (conventional)]
-
A.
nativeRange
Indicates the geographic area where an entity naturally occurs or originated without human introduction.
-
B.
range
chosen
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
C.
hostRange
Indicates the range or set of different hosts that an organism, agent, or system can successfully inhabit, infect, or interact with.
-
D.
rangeCapability
Indicates the maximum distance or extent over which an entity can effectively operate, function, or exert its effect.
-
E.
postalCodeRange
Indicates that one entity specifies a contiguous range of postal codes applicable to another entity or context.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.