Triple
T37460571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mad Scientist |
E930905
|
entity |
| Predicate | putsSecretIntoPlay |
P187922
|
FINISHED |
| Object | From controller deck |
—
|
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: From controller deck | Statement: [Mad Scientist, putsSecretIntoPlay, From controller deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: putsSecretIntoPlay Context triple: [Mad Scientist, putsSecretIntoPlay, From controller deck]
-
A.
secretRevealed
Indicates that previously hidden or confidential information has been disclosed to one or more parties.
-
B.
protagonistSecret
Indicates that one entity is the main character who possesses or is associated with a hidden fact, identity, or piece of information unknown to others.
-
C.
knowsSecret
Indicates that one entity is aware of confidential or hidden information about another entity or situation.
-
D.
seeksSecretFrom
Indicates that one entity is actively trying to obtain hidden or confidential information from another entity.
-
E.
guardedSecretBy
Indicates that a secret is being protected or kept confidential by a specific 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.