Triple
T26551356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天神 |
E671685
|
entity |
| Predicate | 属する都市 |
P24465
|
FINISHED |
| Object | 福岡市 |
—
|
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: 福岡市 | Statement: [天神, 属する都市, 福岡市]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 属する都市 Context triple: [天神, 属する都市, 福岡市]
-
A.
isMetropolitanOf
Indicates that one entity is the primary metropolitan area or major urban center associated with another entity, such as a region, country, or administrative division.
-
B.
cityAssociatedWith
chosen
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
-
C.
metropolitanOf
Indicates that one place serves as the primary metropolitan center or core urban area for another place or region.
-
D.
hasAssociatedCity
Indicates that one entity is linked or related to a specific city, typically as its location, base, or primary area of association.
-
E.
isPartOfCapitalCityOf
Indicates that something is a constituent or component of the capital city belonging to a particular political or administrative entity.
- 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.