Triple
T38477523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Protocol |
E915585
|
entity |
| Predicate | dialogueMechanic |
P139053
|
FINISHED |
| Object | timed dialogue choices |
—
|
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: timed dialogue choices | Statement: [Alpha Protocol, dialogueMechanic, timed dialogue choices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dialogueMechanic Context triple: [Alpha Protocol, dialogueMechanic, timed dialogue choices]
-
A.
dialogueDynamic
Indicates a relationship where entities are engaged in or contributing to an evolving, back-and-forth dialogue or conversational exchange.
-
B.
dialogueFeature
chosen
Indicates that one entity exhibits or involves a particular characteristic, property, or element of a dialogue or conversational exchange with another entity.
-
C.
dialogueAction
Indicates an action performed within a dialogue or conversation between entities, such as speaking, asking, answering, or otherwise verbally interacting.
-
D.
dialogueType
Indicates the specific kind or category of dialogue occurring between entities (e.g., question-answer, negotiation, instruction).
-
E.
dialogue
Indicates that two or more entities are engaged in an exchange of spoken or written communication with each other.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.