Triple
T11989098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiume |
E285357
|
entity |
| Predicate | primaryFunctionInShow |
P83244
|
FINISHED |
| Object | lead songs |
—
|
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: lead songs | Statement: [Kiume, primaryFunctionInShow, lead songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFunctionInShow Context triple: [Kiume, primaryFunctionInShow, lead songs]
-
A.
primaryFunctionInPlot
Indicates the main narrative role or purpose that an entity serves within the plot of a story.
-
B.
primaryFunctionInSeries
chosen
Indicates that an entity serves as the main or most important function within a particular series or sequence.
-
C.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
D.
primaryFunctionContext
Indicates the main situational or operational context in which a function, role, or process is primarily intended to be used or performed.
-
E.
primaryFunctionInPractice
Indicates that an entity serves as the main or most important function or role within a given practical context or real-world usage.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903ae28708190a826bad1624343eb |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.