Triple
T32424575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 三井寺 |
E828543
|
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.
alternativeNameMeaning
Indicates that one entity expresses the meaning or interpretation of an alternative name used for another entity.
-
B.
reasonForEpithet
chosen
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
C.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
D.
usedAsNamesakeFor
Indicates that one entity serves as the source or inspiration for the name given to another entity.
-
E.
nicknamedByJapanese
Indicates that an entity is known or referred to by a particular nickname given by Japanese people or in a Japanese context.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c286ac288190843dac21651babd0 |
completed | May 3, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.