Triple
T37061058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 京都府長岡京市 |
E917324
|
entity |
| Predicate | 属する地域 |
P86016
|
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.
所在地エリア
Indicates the geographical area or region in which an entity is located or based.
-
B.
associatedAdministrativeRegion
Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
-
C.
regionOfAssociation
chosen
Indicates a broader geographic or spatial area with which an entity is functionally, contextually, or organizationally associated.
-
D.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
E.
関与地域
Indicates a geographical area or region that is involved in, affected by, or relevant to a particular activity, event, or relationship.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.