Triple
T28728582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markovo |
E730291
|
entity |
| Predicate | locatedInPermafrostRegion |
P15762
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Markovo, locatedInPermafrostRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPermafrostRegion Context triple: [Markovo, locatedInPermafrostRegion, true]
-
A.
hasPermafrost
chosen
Indicates that a location or area contains ground that remains continuously frozen (permafrost) for an extended period.
-
B.
locatedInSubarcticRegion
Indicates that something exists or occurs within a subarctic geographic region characterized by cold climates just south of the Arctic.
-
C.
permafrostDepth
Indicates the measured or estimated thickness or vertical extent of perennially frozen ground (permafrost) at a given location.
-
D.
locatedAtPoleRegion
Indicates that an entity is situated within a polar region of a planetary body, such as its north or south pole area.
-
E.
isWithinArcticCircle
Indicates that one geographic entity lies inside the boundary of the Arctic Circle region.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: April 28, 2026, 5:57 a.m.