Triple
T32776460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Reimer |
E838220
|
entity |
| Predicate | hasPermanentResearchStation |
P138582
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Mount Reimer, hasPermanentResearchStation, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPermanentResearchStation Context triple: [Mount Reimer, hasPermanentResearchStation, false]
-
A.
hasPermanentResearchStations
chosen
Indicates that one entity maintains long-term, continuously operating research facilities within the domain or territory of another entity.
-
B.
establishedResearchStation
Indicates that an entity founded or set up a research station at a particular location or for a particular purpose.
-
C.
maintainedResearchStation
Indicates that an entity was responsible for operating, supporting, or keeping a research station in working condition over a period of time.
-
D.
containsResearchStation
Indicates that one entity geographically includes or hosts a research station within its boundaries.
-
E.
hasNearbyResearchStations
Indicates that one entity has research stations located in close geographical proximity to it.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 1, 2026, 1:13 a.m.