Triple
T37061436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 男山 |
E917333
|
entity |
| Predicate | 位置特性 |
P80113
|
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 act of determining or establishing the position, location, or placement of one entity relative to a reference point or context.
-
B.
立地特性
chosen
Indicates the characteristics or qualities of a location that define its situational conditions or advantages in relation to its surroundings.
-
C.
生态定位
Indicates the ecological role or niche an organism occupies within its environment, including its functional position and interactions in the ecosystem.
-
D.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
E.
positionOnEnvironment
Indicates the spatial placement or location of an entity relative to a surrounding environment or surface.
- 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.