Triple
T32317057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kantokuen |
E825666
|
entity |
| Predicate | regionOfPlanning |
P55551
|
FINISHED |
| Object | Tokyo |
—
|
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 | Statement: [Kantokuen, regionOfPlanning, Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfPlanning Context triple: [Kantokuen, regionOfPlanning, Tokyo]
-
A.
partOfPlanningRegion
chosen
Indicates that one entity is included within, or belongs to, a larger designated planning region.
-
B.
plannedArea
Indicates that an area is designated or intended for a specific planned use or development.
-
C.
regionTypePlanned
Indicates that a region is intended or designated to have a specific type or classification in a planned or future state.
-
D.
regionalPlanningInstrument
Indicates that an entity is a formal tool, policy, or framework used to guide and regulate planning and development within a specific geographic region.
-
E.
locationOfPlanning
Indicates the place or setting where the planning activity or process occurs.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 1, 2026, 12:46 a.m.