Triple
T218873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Nights |
E4169
|
entity |
| Predicate | hasLatitudeCondition |
P1255
|
FINISHED |
| Object | high northern latitude |
—
|
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: high northern latitude | Statement: [White Nights, hasLatitudeCondition, high northern latitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatitudeCondition Context triple: [White Nights, hasLatitudeCondition, high northern latitude]
-
A.
hasCondition
chosen
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
B.
coordinateLatitude
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
-
C.
coordinateLongitude
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
D.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
E.
hasCoordinateSingularity
Indicates that something possesses a point or region where its coordinate description becomes undefined or degenerate, even if the underlying object or space may remain well-behaved.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c5199d8819096736c11077adec3 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.