Triple
T3474458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campo de Hielo Norte |
E73336
|
entity |
| Predicate | hasAblationZone |
P6793
|
FINISHED |
| Object | termini of outlet glaciers |
—
|
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: termini of outlet glaciers | Statement: [Campo de Hielo Norte, hasAblationZone, termini of outlet glaciers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAblationZone Context triple: [Campo de Hielo Norte, hasAblationZone, termini of outlet glaciers]
-
A.
hasZone
chosen
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
hasDRSZones
Indicates that one entity possesses, defines, or is associated with specific DRS (Disaster Recovery Site or similarly defined) zones.
-
C.
hasFreeZone
Indicates that an entity includes or is associated with a designated free zone area where special rules, privileges, or exemptions apply.
-
D.
hasTissue
Indicates that one entity possesses, contains, or is associated with a specific tissue of another entity.
-
E.
hasProtectedAreaAlongCourse
Indicates that a segment of the course or route passes through or borders a designated protected area.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb580d4c819080bcc0bccd1e18e2 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.