Triple
T10260237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | This Masquerade |
E240574
|
entity |
| Predicate | featuresScatSingingInNotableVersion |
P33230
|
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: [This Masquerade, featuresScatSingingInNotableVersion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresScatSingingInNotableVersion Context triple: [This Masquerade, featuresScatSingingInNotableVersion, true]
-
A.
notableSongCharacteristic
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
B.
singsAbout
Indicates that one entity performs a song whose subject or theme is another entity.
-
C.
vocalPerformanceNotedFor
chosen
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
-
D.
notableSongsIncluded
Indicates that certain notable or significant songs are included as part of the referenced entity (such as an album, playlist, or collection).
-
E.
notableChorus
Indicates that an entity is recognized for having a particularly prominent or distinguished chorus section.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:32 a.m.