Triple
T23595178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Masked Dancer |
E582592
|
entity |
| Predicate | hasRevealMechanism |
P11155
|
FINISHED |
| Object | unmasking of eliminated contestants |
—
|
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: unmasking of eliminated contestants | Statement: [The Masked Dancer, hasRevealMechanism, unmasking of eliminated contestants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevealMechanism Context triple: [The Masked Dancer, hasRevealMechanism, unmasking of eliminated contestants]
-
A.
hasModeOfRevelation
chosen
Indicates the manner or channel through which something is revealed, communicated, or made known.
-
B.
isRevealedTo
Indicates that previously hidden or unknown information becomes known to a specific entity or group.
-
C.
hasTriggerMechanism
Indicates that an entity possesses or is equipped with a specific mechanism used to initiate or activate an action or process.
-
D.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
E.
isRevealedIn
Indicates that something becomes known, disclosed, or made apparent within a particular context, medium, or situation.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08e9aa4819091099dfc2074b22d |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.