Triple
T27782364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back to the Future: The Game |
E699366
|
entity |
| Predicate | hasDialogueTrees |
P184842
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Back to the Future: The Game, hasDialogueTrees, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialogueTrees Context triple: [Back to the Future: The Game, hasDialogueTrees, true]
-
A.
hasDialogueTrait
Indicates that an entity possesses a specific characteristic or quality related to dialogue or conversational behavior.
-
B.
hasDialogueSystem
Indicates that an entity includes or is equipped with a system for managing dialogue or conversational interactions.
-
C.
hasDialogueIn
Indicates that an entity participates in or contains spoken or written dialogue within a specified context, such as a scene, work, or medium.
-
D.
hasMultilingualDialogue
Indicates that an interaction or work contains dialogue expressed in more than one language.
-
E.
hasDialogueFunction
Indicates that an utterance or segment of discourse serves a specific communicative role or function within a dialogue (e.g., question, answer, request, acknowledgment).
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 27, 2026, 5:11 p.m.