Triple
T21463741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crac |
E529537
|
entity |
| Predicate | isSilentOrMinimalDialogue |
P49712
|
FINISHED |
| Object | yes |
—
|
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 | Statement: [Crac, isSilentOrMinimalDialogue, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSilentOrMinimalDialogue Context triple: [Crac, isSilentOrMinimalDialogue, yes]
-
A.
hasNoSpokenDialogue
chosen
Indicates that the referenced entity does not produce any spoken dialogue within the given context or work.
-
B.
isSilentWithMusic
Indicates that an entity remains quiet or produces no audible sound when music is playing.
-
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.
hasDialogueTrait
Indicates that an entity possesses a specific characteristic or quality related to dialogue or conversational behavior.
-
E.
hasDialogueSystem
Indicates that an entity includes or is equipped with a system for managing dialogue or conversational interactions.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9f100fc819093999018f7d78443 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.