Triple
T37864775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 嵐電（京福電気鉄道嵐山本線） |
E944439
|
entity |
| Predicate | 愛称の由来 |
P9593
|
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.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
-
B.
reasonForEpithet
chosen
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
C.
nicknameOfFormation
Indicates that one name is an informal or colloquial nickname used to refer to a particular formation.
-
D.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
E.
nameGivesRiseTo
Indicates that one name, term, or designation leads to, causes, or results in the emergence or establishment of another.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.