Triple
T23941948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yodogawa Ward Office |
E602804
|
entity |
| Predicate | administrativeAreaServed |
P82
|
FINISHED |
| Object | Yodogawa-ku |
—
|
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: Yodogawa-ku | Statement: [Yodogawa Ward Office, administrativeAreaServed, Yodogawa-ku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeAreaServed Context triple: [Yodogawa Ward Office, administrativeAreaServed, Yodogawa-ku]
-
A.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
B.
strategicAreaServed
Indicates that an entity provides services or exerts influence within a particular area considered strategically important.
-
C.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
D.
townServed
Indicates that a given service, facility, or infrastructure serves or provides coverage to a particular town.
-
E.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02ae4e4819083c0e160395b6fea |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:09 p.m.