Triple
T10722379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvera |
E252853
|
entity |
| Predicate | hasDialogueIn |
P95630
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Calvera, hasDialogueIn, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialogueIn Context triple: [Calvera, hasDialogueIn, English]
-
A.
hasDialogueTrait
Indicates that an entity possesses a specific characteristic or quality related to dialogue or conversational behavior.
-
B.
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).
-
C.
hasProseDialogue
Indicates that one entity contains or features spoken or conversational content expressed in prose form involving another entity.
-
D.
hasNoSpokenDialogue
Indicates that the referenced entity does not produce any spoken dialogue within the given context or work.
-
E.
dialoguesBy
Indicates that one entity is the creator, author, or source of the dialogues associated with another entity.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70d44d0048190a78aae2357e864a5 |
completed | April 9, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:13 p.m.