Triple
T22922727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 木津川市 |
E568907
|
entity |
| Predicate | isResidentialCityOf |
P70992
|
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: [木津川市, isResidentialCityOf, 京都市都市圏]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResidentialCityOf Context triple: [木津川市, isResidentialCityOf, 京都市都市圏]
-
A.
isResidentialTown
Indicates that a town is primarily used or designated for residential living rather than for commercial, industrial, or other primary purposes.
-
B.
isResidentialBaseFor
Indicates that a location serves as the primary place of residence or home base for a person or group.
-
C.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
D.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
E.
isCityOf
chosen
Indicates that one entity is a city that belongs to, is located within, or is administratively part of another entity (such as a country, state, or region).
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d6841c81908df6d4e501860a15 |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:43 p.m.