Triple
T1195480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shibuya Station |
E25657
|
entity |
| Predicate | hasMapCoordinateSystem |
P22467
|
FINISHED |
| Object | WGS84 |
—
|
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: WGS84 | Statement: [Shibuya Station, hasMapCoordinateSystem, WGS84]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapCoordinateSystem Context triple: [Shibuya Station, hasMapCoordinateSystem, WGS84]
-
A.
hasCoordinates
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
B.
hasCoordinatesType
chosen
Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
-
C.
hasMapReference
Indicates that an entity is associated with a specific map or map location reference.
-
D.
isOnSystemMap
Indicates that an entity is currently displayed or represented on a particular system map.
-
E.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd78f61c8190bdba2255d35a8fe4 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.