Triple
T38593896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hana Song |
E932516
|
entity |
| Predicate | isStreamerInLore |
P113838
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hana Song, isStreamerInLore, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStreamerInLore Context triple: [Hana Song, isStreamerInLore, true]
-
A.
isStreamer
chosen
Indicates that the subject regularly broadcasts live content over an online streaming platform.
-
B.
seriesLore
Indicates that one entity provides backstory, world-building, or canonical background information that enriches the overarching narrative of a series in which the other entity appears.
-
C.
hasLoreContext
Indicates that something is associated with or situated within a particular narrative, historical, or fictional background or storyline.
-
D.
isSideStoryTo
Indicates that one narrative work is a supplementary or tangential story that expands on, but is not central to, the main storyline of another work.
-
E.
inGameLoreSource
Indicates that the information or content originates from narrative or explanatory material within the game’s own lore or story universe.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.