Triple
T30441616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大阪府豊中市 |
E774459
|
entity |
| Predicate | 施行時特例市 |
P4405
|
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.
specialMunicipality
chosen
Indicates that an entity is designated as a special municipality, typically having a distinct administrative or legal status compared to regular municipalities.
-
B.
isPrefecturalCityOf
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
C.
prefecture-levelCity
Indicates that one entity is a city that holds prefecture-level administrative status in relation to another entity (typically a higher-level region or governing structure).
-
D.
isPrefectureOfItself
Indicates that an administrative unit is considered a prefecture in its own right, rather than being part of another prefecture.
-
E.
isGovernmentOrdinanceDesignatedCity
Indicates that a city has been officially designated as a government ordinance–designated city by the national government.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6869948e481908901dbda23952cc0 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:08 p.m.