Triple
T21968602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 高崎駅 |
E542522
|
entity |
| Predicate | エリア内位置付け |
P91855
|
FINISHED |
| Object | 北関東有数のターミナル駅 |
—
|
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: 北関東有数のターミナル駅 | Statement: [高崎駅, エリア内位置付け, 北関東有数のターミナル駅]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: エリア内位置付け Context triple: [高崎駅, エリア内位置付け, 北関東有数のターミナル駅]
-
A.
locationPosed
chosen
Indicates that an entity is positioned or situated at a specific location.
-
B.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
C.
locationOnSquare
Indicates that one entity is positioned on a specific square region or cell within a larger spatial grid or board.
-
D.
locationServices
Indicates that one entity provides, enables, or manages geographic positioning or place-related functionalities for another entity.
-
E.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1245d50d08190a4bf93139daa77eb |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8:02 p.m.