Triple
T28498850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Metropolitan Routes |
E721178
|
entity |
| Predicate | hasMapPublisher |
P198162
|
FINISHED |
| Object | Tokyo Metropolitan Government |
—
|
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: Tokyo Metropolitan Government | Statement: [Tokyo Metropolitan Routes, hasMapPublisher, Tokyo Metropolitan Government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapPublisher Context triple: [Tokyo Metropolitan Routes, hasMapPublisher, Tokyo Metropolitan Government]
-
A.
hasMapState
Indicates that an entity is associated with a particular state or condition of a map (such as its configuration, status, or version).
-
B.
hasMapReference
Indicates that an entity is associated with a specific map or map location reference.
-
C.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
-
D.
hasMapBy
Indicates that one entity is represented, depicted, or detailed by a specific map associated with it.
-
E.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
| PDg | Predicate description generation | batch_69feced436a48190b761db7df2d6b6bd |
completed | May 9, 2026, 6:06 a.m. |
Created at: April 28, 2026, 3:05 a.m.