Triple
T21106023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Epsilon |
E520044
|
entity |
| Predicate | latitudeOfFormationApprox |
P9311
|
FINISHED |
| Object | about 30°N |
—
|
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: about 30°N | Statement: [Hurricane Epsilon, latitudeOfFormationApprox, about 30°N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latitudeOfFormationApprox Context triple: [Hurricane Epsilon, latitudeOfFormationApprox, about 30°N]
-
A.
firstKnownLocationOnEarth
Indicates the earliest known place on Earth where the entity was present, discovered, or recorded.
-
B.
lunarLatitude
Indicates the angular distance of a point on the Moon north or south of the lunar equator.
-
C.
hasApproximateDistanceFromEquator
chosen
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
-
D.
ascendingNodeLongitude
Indicates the angular position, measured in longitude, of an orbiting body's ascending node where it crosses from south to north of a reference plane.
-
E.
distanceFromEquator
Indicates how far a location is from the Earth's equator, typically measured as a geographic or angular distance.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b62301c819082cfc6cb3cd11c8c |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.