Triple
T37060670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 奈良県生駒市 |
E917314
|
entity |
| Predicate | 主要山 |
P122462
|
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 that multiple mountain peaks are connected in a continuous range or chain.
-
B.
hasMainMountain
chosen
Indicates that an entity is primarily associated with or characterized by a specific mountain as its main or most significant mountain.
-
C.
本山
Indicates a relationship or action involving "Benshan," but the predicate alone is too ambiguous to determine a specific relational meaning without additional context.
-
D.
parentMountain
Indicates that one mountain is considered the larger or primary "parent" from which another, related "child" mountain is derived or associated.
-
E.
mainHillName
Indicates that the subject’s primary or most prominent hill is identified by the given name.
- 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.