Triple
T29304710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishikari Plain |
E743059
|
entity |
| Predicate | capitalCityLocatedHere |
P119577
|
FINISHED |
| Object | Sapporo |
—
|
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: Sapporo | Statement: [Ishikari Plain, capitalCityLocatedHere, Sapporo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityLocatedHere Context triple: [Ishikari Plain, capitalCityLocatedHere, Sapporo]
-
A.
capitalOfRegionLocatedHere
chosen
Indicates that a place serves as the capital of a region that is geographically located at or associated with this place.
-
B.
capitalLocation
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic entity.
-
C.
capitalOftenLocatedIn
Indicates that the capital city of a region or country is frequently, though not always, situated within a particular location or type of area.
-
D.
capitalCityResidenceOf
Indicates that a person or entity resides in the capital city of a specified country or region.
-
E.
capitalCityInvolved
Indicates that a capital city participates in, is affected by, or plays a role in a specified event, process, or relationship.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 28, 2026, 1:12 p.m.