Triple
T37060756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天野川 |
E917316
|
entity |
| Predicate | 別名の由来 |
P178534
|
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.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
C.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
D.
hasAlternativeNamesakeRole
Indicates that an entity serves in an additional or alternative role as a namesake, distinct from its primary namesake role.
-
E.
alsoKnownAsReason
chosen
Indicates that an alternative name or alias is used for an entity specifically because of the stated reason.
- 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.