Triple
T31392130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronic Sound |
E800758
|
entity |
| Predicate | subLabel |
P171685
|
FINISHED |
| Object | Zapple |
—
|
NE NERFINISHED |
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: Zapple | Statement: [Electronic Sound, subLabel, Zapple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subLabel Context triple: [Electronic Sound, subLabel, Zapple]
-
A.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
B.
subtheme
Indicates that one topic or concept functions as a more specific, subordinate theme within a broader overarching theme.
-
C.
subLeader
Indicates that one entity serves as a subordinate or deputy leader under the authority of another leader entity.
-
D.
subMode
Indicates a more specific or subordinate mode that falls under or refines a broader, parent mode within a hierarchy of modes.
-
E.
subtitleDFunction
Indicates a functional relationship where one entity serves as the subtitle or secondary textual label for another entity.
- F. None of above. chosen
Provenance (4 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:19 p.m.