Triple
T26551395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天神 |
E671685
|
entity |
| Predicate | 都市計画 |
P7886
|
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.
urbanPlanBy
Indicates that an urban plan is created, designed, or authored by a specific agent or authority.
-
B.
cityOfPlanning
Indicates the city where the planning or design activities for something (e.g., a project, event, or development) are carried out.
-
C.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
D.
mainUrbanPlan
Indicates the primary urban planning scheme or framework that governs the development and organization of a given area.
-
E.
urbanDevelopment
chosen
Indicates the process or activities through which urban areas are planned, expanded, or transformed, including changes to infrastructure, land use, and the built environment.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f614624c80819084f6febf57f86828 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:47 a.m.