Triple
T37060798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 交野山 |
E917317
|
entity |
| Predicate | 周辺 |
P17801
|
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.
surrounds
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
B.
around
chosen
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
C.
surroundedOnThreeSidesBy
Indicates that one entity is positioned so that three of its sides are directly bordered or enclosed by another entity.
-
D.
isOftenLocatedAround
Indicates that one entity is frequently found in the vicinity of, or surrounding, another entity.
-
E.
isLocatedOnOutskirtsOf
Indicates that one entity is situated on the outer edge or peripheral area of another entity, rather than in its central or inner part.
- 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.