Triple
T26185904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Antarctic Ice Sheet |
E654826
|
entity |
| Predicate | hasResearchStationsOn |
P2881
|
FINISHED |
| Object | Concordia Station |
—
|
NE NERFINISHED |
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: Concordia Station | Statement: [East Antarctic Ice Sheet, hasResearchStationsOn, Concordia Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchStationsOn Context triple: [East Antarctic Ice Sheet, hasResearchStationsOn, Concordia Station]
-
A.
hasPermanentResearchStations
Indicates that one entity maintains long-term, continuously operating research facilities within the domain or territory of another entity.
-
B.
hasNearbyResearchStations
Indicates that one entity has research stations located in close geographical proximity to it.
-
C.
hasResearchCentersIn
Indicates that an entity maintains or operates research centers located within a specified place or region.
-
D.
containsResearchStation
chosen
Indicates that one entity geographically includes or hosts a research station within its boundaries.
-
E.
establishedResearchStation
Indicates that an entity founded or set up a research station at a particular location or for a particular purpose.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 26, 2026, 8:42 p.m.