Triple
T25122654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Master’s Voice |
E629306
|
entity |
| Predicate | fictionalProject |
P134760
|
FINISHED |
| Object | His Master’s Voice project |
—
|
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: His Master’s Voice project | Statement: [His Master’s Voice, fictionalProject, His Master’s Voice project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalProject Context triple: [His Master’s Voice, fictionalProject, His Master’s Voice project]
-
A.
fictionalContent
Indicates that one entity is content whose subject matter, events, or characters are imaginary or invented rather than factual.
-
B.
projectInNovel
Indicates that a specific project appears within, is described in, or is otherwise part of the content of a particular novel.
-
C.
fictionalSon
Indicates that one entity is portrayed as the son of another entity within a fictional or narrative context.
-
D.
fictionalInvention
chosen
Indicates that one entity is an invention or creation that exists only within the fictional context of another entity (such as a story, universe, or work).
-
E.
fictionalField
Indicates that the subject is associated with a fictional or imaginary field, domain, or area rather than a real-world one.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 6:28 a.m.