Triple
T22022577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magic 8 Ball |
E543878
|
entity |
| Predicate | hasInteractionMode |
P146301
|
FINISHED |
| Object | physical |
—
|
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: physical | Statement: [Magic 8 Ball, hasInteractionMode, physical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteractionMode Context triple: [Magic 8 Ball, hasInteractionMode, physical]
-
A.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
B.
hasInteractiveActivity
Indicates that an entity includes or is associated with an activity that requires active user participation or engagement.
-
C.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
D.
supportsInteractiveMenus
Indicates that an entity provides or is compatible with interactive, menu-based user interfaces or options.
-
E.
hasModeConnection
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
- 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.