Triple
T19541152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Pendragon |
E488903
|
entity |
| Predicate | isInAntarcticRegion |
P136710
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mount Pendragon, isInAntarcticRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInAntarcticRegion Context triple: [Mount Pendragon, isInAntarcticRegion, true]
-
A.
isInSubantarcticRegion
Indicates that an entity is located within the subantarctic geographic region, typically just north of the Antarctic Circle.
-
B.
containsAntarcticTerritory
Indicates that a geopolitical entity includes land or territory located within the Antarctic region.
-
C.
claimedInAntarcticaBetweenMeridians
Indicates that a territorial claim in Antarctica lies within the longitudinal range defined by the specified meridians.
-
D.
locatedAtPoleRegion
Indicates that an entity is situated within a polar region of a planetary body, such as its north or south pole area.
-
E.
isWithinArcticCircle
Indicates that one geographic entity lies inside the boundary of the Arctic Circle region.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63872fda48190bbb1f465cb7b57fe |
completed | April 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:41 p.m.