Triple
T7474023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tropical Northwestern Atlantic |
E176582
|
entity |
| Predicate | isLocatedInLatitudeZone |
P13005
|
FINISHED |
| Object | tropics |
—
|
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: tropics | Statement: [Tropical Northwestern Atlantic, isLocatedInLatitudeZone, tropics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInLatitudeZone Context triple: [Tropical Northwestern Atlantic, isLocatedInLatitudeZone, tropics]
-
A.
liesWithinLatitudeBand
chosen
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
B.
hasTropicOfCancerCrossing
Indicates that the specified entity is geographically intersected or crossed by the Tropic of Cancer.
-
C.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
D.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
E.
isInWesternPartOf
Indicates that one entity is located within the western part or region of another entity.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f417fbb48190b134eaf1da1b4289 |
completed | March 27, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:41 p.m.