Triple
T22022549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magic 8 Ball |
E543878
|
entity |
| Predicate | typicalAnswerType |
P146299
|
FINISHED |
| Object | yes-or-no |
—
|
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: yes-or-no | Statement: [Magic 8 Ball, typicalAnswerType, yes-or-no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAnswerType Context triple: [Magic 8 Ball, typicalAnswerType, yes-or-no]
-
A.
typicalQuestion
Indicates that an entity is a common or standard question typically asked in a given context or situation.
-
B.
typicalResponse
Indicates that an entity’s behavior, reaction, or outcome is the standard or commonly expected response in a given context or situation.
-
C.
questionType
Indicates the specific category or kind of question that an item, query, or prompt belongs to.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c8ac6881909a9e96e0873a3ae2 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:23 p.m.