Triple
T17994146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Ocean |
E430455
|
entity |
| Predicate | inSouthernHemisphere |
P26576
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Atlantic Ocean, inSouthernHemisphere, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inSouthernHemisphere Context triple: [Atlantic Ocean, inSouthernHemisphere, true]
-
A.
directionInSouthernHemisphere
Indicates that the specified direction is defined or measured relative to locations or reference frames in the Southern Hemisphere.
-
B.
locatedInTheSouthernHemisphere
chosen
Indicates that the subject is situated geographically south of the Earth's equator.
-
C.
hasSeasonalPositionSouthernHemisphere
Indicates that an entity’s seasonal position or phase is defined specifically with respect to conditions in the Southern Hemisphere.
-
D.
typicalSeasonSouthernHemisphere
Indicates the season in the Southern Hemisphere during which something most commonly or characteristically occurs.
-
E.
isSouthernHemisphereTimeZone
Indicates that a time zone is located in, or primarily associated with, the Southern Hemisphere.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e29490819090ff221e7d7a9ddd |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.