Triple
T9296329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Futaba, Fukushima Prefecture |
E223646
|
entity |
| Predicate | locatedInDirectionFromTokyo |
P87488
|
FINISHED |
| Object | northeast |
—
|
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: northeast | Statement: [Futaba, Fukushima Prefecture, locatedInDirectionFromTokyo, northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionFromTokyo Context triple: [Futaba, Fukushima Prefecture, locatedInDirectionFromTokyo, northeast]
-
A.
distanceFromTokyo
Indicates the physical distance between a given location and Tokyo.
-
B.
distanceFromKochi_km
Indicates the physical distance, measured in kilometers, between a given location and Kochi.
-
C.
distanceFromNaha
Indicates the spatial distance between a given location and Naha.
-
D.
distanceToSapporo
Indicates the measured or calculated distance between a given entity and the location of Sapporo.
-
E.
locatedInPrefectureCapitalRegion
Indicates that the subject is geographically situated within the capital region of a given prefecture.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089c9c588190967404c9eb938dfb |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:36 p.m.