Triple
T27069639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oshiage district |
E685286
|
entity |
| Predicate | cityWard |
P76280
|
FINISHED |
| Object | Sumida City |
—
|
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: Sumida City | Statement: [Oshiage district, cityWard, Sumida City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityWard Context triple: [Oshiage district, cityWard, Sumida City]
-
A.
locatedInCityWard
chosen
Indicates that one entity is situated within the administrative boundaries of a specific city ward.
-
B.
municipalWardType
Indicates the specific category or classification of a municipal ward within a local government or administrative structure.
-
C.
citySubdivision
Indicates that one administrative or geographic unit is a smaller subdivision contained within a larger city.
-
D.
specialWard
Indicates that an entity is designated as a special ward, typically signifying a distinct administrative or jurisdictional subdivision with special status.
-
E.
inCityDistrict
Indicates that one entity is located within the boundaries of a specific city district.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623107cf08190af1660cd6987c912 |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:27 a.m.