Triple
T29156613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makanrushi |
E739061
|
entity |
| Predicate | hasNearbyMajorLandmass |
P167255
|
FINISHED |
| Object | Kamchatka Peninsula |
—
|
NE NERFINISHED |
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: Kamchatka Peninsula | Statement: [Makanrushi, hasNearbyMajorLandmass, Kamchatka Peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMajorLandmass Context triple: [Makanrushi, hasNearbyMajorLandmass, Kamchatka Peninsula]
-
A.
nearbyMajorLandmass
chosen
Indicates that one entity is geographically close to a large, significant landmass such as a continent or major island.
-
B.
nearestLandmass
Indicates that one landmass is the closest geographically to another specified point or landmass.
-
C.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
D.
hasNearbyMarineFeature
Indicates that one entity is located close to a marine geographic feature associated with the other entity.
-
E.
onLandmass
Indicates that one entity is physically located on or within the boundaries of a specified landmass.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 28, 2026, 11:45 a.m.