Triple
T31810792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyasina Bay |
E811999
|
entity |
| Predicate | adjacentTerrestrialBiome |
P181168
|
FINISHED |
| Object | Arctic tundra |
—
|
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: Arctic tundra | Statement: [Pyasina Bay, adjacentTerrestrialBiome, Arctic tundra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentTerrestrialBiome Context triple: [Pyasina Bay, adjacentTerrestrialBiome, Arctic tundra]
-
A.
adjacentLandform
Indicates that two landforms are directly next to each other in space, sharing a common boundary or lying in immediate proximity.
-
B.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
C.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
D.
neighboringRegion
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
-
E.
neighboringIsland
Indicates that one island is geographically adjacent to or very close to another island, typically separated only by a narrow body of water.
- F. None of above. chosen
Provenance (4 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 30, 2026, 11:43 p.m.