Triple
T2220604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heezen Glacier |
E48130
|
entity |
| Predicate | hasTypeOfLocation |
P6822
|
FINISHED |
| Object | natural geographic feature |
—
|
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: natural geographic feature | Statement: [Heezen Glacier, hasTypeOfLocation, natural geographic feature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfLocation Context triple: [Heezen Glacier, hasTypeOfLocation, natural geographic feature]
-
A.
hasMainLocationType
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
-
B.
hasTypeLocality
Indicates the specific geographic location where an entity (typically a species or specimen) was originally found and formally described.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
E.
hasAreaType
chosen
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0156c8c819083e3e3b6ede1e951 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.