Triple
T25919204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Alexandra Range |
E653119
|
entity |
| Predicate | usedAsRoute |
P141321
|
FINISHED |
| Object | historic route to Antarctic Plateau |
—
|
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: historic route to Antarctic Plateau | Statement: [Queen Alexandra Range, usedAsRoute, historic route to Antarctic Plateau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsRoute Context triple: [Queen Alexandra Range, usedAsRoute, historic route to Antarctic Plateau]
-
A.
usedRoutes
Indicates that an entity has utilized or traveled along specific routes.
-
B.
currentUseOfRoute
Indicates that a particular route is presently being used for a specific purpose, activity, or traffic flow.
-
C.
servesAsRouteTo
chosen
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
D.
usesRoutingType
Indicates that one entity employs or operates according to a specific routing type or routing method associated with another entity.
-
E.
usageRoute
Indicates the path, method, or channel through which something is used, applied, or accessed.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 22, 2026, 8:31 a.m.