Triple
T7266541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suga no Uta |
E160987
|
entity |
| Predicate | settingInMyth |
P58483
|
FINISHED |
| Object | Suga in Izumo |
—
|
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: Suga in Izumo | Statement: [Suga no Uta, settingInMyth, Suga in Izumo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingInMyth Context triple: [Suga no Uta, settingInMyth, Suga in Izumo]
-
A.
settingOfMyth
chosen
Indicates that a location or environment serves as the backdrop or context in which a particular myth takes place.
-
B.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
C.
settingControlled
Indicates that one entity regulates, adjusts, or determines the configuration or parameters of another entity.
-
D.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
E.
signalsSetting
Indicates that one entity conveys or triggers information about a particular setting or configuration for another entity.
- 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:58 p.m.