Triple
T408766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Pole |
E9439
|
entity |
| Predicate | isDifficultToAccessBecauseOf |
P11058
|
FINISHED |
| Object | drifting ice |
—
|
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: drifting ice | Statement: [North Pole, isDifficultToAccessBecauseOf, drifting ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDifficultToAccessBecauseOf Context triple: [North Pole, isDifficultToAccessBecauseOf, drifting ice]
-
A.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
B.
accessible
Indicates that one entity can be reached, entered, used, or understood by another entity, often without undue difficulty or barriers.
-
C.
hasStepFreeAccess
Indicates that a location, facility, or route can be accessed without using stairs, typically via ramps, lifts, or level entrances.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
E.
hasMeasurementDifficulty
Indicates that performing a measurement on something is challenging or problematic in some way.
- F. None of above. chosen
Provenance (4 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbf0650819080753815ca280eec |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e971a3a481909e6b075f25dd234a |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea4545608190898436c72e10f39d |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.