Triple
T32193818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystic Seer machine |
E822345
|
entity |
| Predicate | answerStyle |
P173305
|
FINISHED |
| Object | cryptic yes-or-no responses |
—
|
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: cryptic yes-or-no responses | Statement: [Mystic Seer machine, answerStyle, cryptic yes-or-no responses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: answerStyle Context triple: [Mystic Seer machine, answerStyle, cryptic yes-or-no responses]
-
A.
questionStyle
Indicates the manner or format in which a question is posed or expressed.
-
B.
typicalAnswerType
Indicates the usual or expected kind of entity or value that serves as an answer to a given question or query.
-
C.
asksAndAnswersFormat
Indicates that the same entity both poses a question and provides its answer, typically in a structured or predefined format.
-
D.
answerGiven
Indicates that a response or solution has been provided to a question, request, or problem.
-
E.
canAnswerQuestionsIn
Indicates that an entity has the ability to answer questions within a specified context, domain, or environment.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb35369c8190992fe7dad36a2a9d |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b42902a081909126c7322858a2b3 |
completed | May 3, 2026, 2:34 a.m. |
Created at: May 1, 2026, 12:35 a.m.