Triple
T30269288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Lopatka |
E769740
|
entity |
| Predicate | marksNorthernBoundaryOf |
P13331
|
FINISHED |
| Object | Kuril Islands chain |
—
|
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: Kuril Islands chain | Statement: [Cape Lopatka, marksNorthernBoundaryOf, Kuril Islands chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksNorthernBoundaryOf Context triple: [Cape Lopatka, marksNorthernBoundaryOf, Kuril Islands chain]
-
A.
northernBoundaryReference
chosen
Indicates the feature or element that serves as the reference for defining the northern boundary of something.
-
B.
northernBoundaryExtendedTo
Indicates that the northern boundary of one entity has been lengthened or expanded to reach or include another specified reference point or area.
-
C.
boundaryTypeNorth
Indicates that one entity serves as or defines the northern boundary type or classification of another entity.
-
D.
northernBorderLiesAcross
Indicates that the northern border of one region extends across or passes through the area of another region.
-
E.
borderingPoliticalEntityNorth
Indicates that one political entity lies directly to the north of, and shares a border with, another political entity.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680d3816c81909c6ae97dac7ad7f7 |
completed | May 2, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:43 p.m.