Triple
T15681334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gozer |
E377582
|
entity |
| Predicate | formChoiceQuestion |
P50558
|
FINISHED |
| Object | "Choose the form of the Destructor" |
—
|
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: "Choose the form of the Destructor" | Statement: [Gozer, formChoiceQuestion, "Choose the form of the Destructor"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formChoiceQuestion Context triple: [Gozer, formChoiceQuestion, "Choose the form of the Destructor"]
-
A.
questionForm
Indicates that one entity is expressed or structured in the form of a question directed toward another entity or context.
-
B.
questionFormulation
Indicates that one entity formulates, poses, or expresses a question directed toward another entity or context.
-
C.
requiresChoiceBetween
chosen
Indicates that one must select between two or more specified options, and that making such a choice is necessary in the given context.
-
D.
questionSelectionMethod
Indicates how questions are chosen or determined from a set of possible questions.
-
E.
questionPresented
Indicates that a question has been posed or displayed to an entity for consideration or response.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f306a1c8190a819541a3cc51f5a |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.