Triple
T37551736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borean Tundra |
E933604
|
entity |
| Predicate | zoneFeature |
P132063
|
FINISHED |
| Object | Coldarra subzone |
—
|
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: Coldarra subzone | Statement: [Borean Tundra, zoneFeature, Coldarra subzone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneFeature Context triple: [Borean Tundra, zoneFeature, Coldarra subzone]
-
A.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
B.
zoneDesign
Indicates a relationship where an entity defines, specifies, or configures the design or layout of a particular zone or area.
-
C.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
-
D.
zoneLabel
Indicates that a specific label or name is assigned to a defined zone or area within a larger context.
-
E.
zonesInclude
chosen
Indicates that one zone spatially or logically contains or encompasses another zone.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.