Triple
T29011619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SelectDialogItemText |
E736579
|
entity |
| Predicate | typicalCaller |
P203306
|
FINISHED |
| Object | application code handling dialog events |
—
|
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: application code handling dialog events | Statement: [SelectDialogItemText, typicalCaller, application code handling dialog events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCaller Context triple: [SelectDialogItemText, typicalCaller, application code handling dialog events]
-
A.
callType
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
-
B.
typicalSpeaker
Indicates that the subject is a prototypical or characteristic speaker or source of utterances in the context of the object.
-
C.
callingStyle
Indicates the manner or convention by which one entity initiates or performs a call or invocation on another entity.
-
D.
typeOfCallCenter
Indicates the specific category or kind of call center associated with or operated by an entity.
-
E.
callsTo
Indicates that one entity initiates a call or communication action directed toward 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a01531add1c8190b51add7bb046e2cb |
completed | May 11, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_6a014fef3d8c81909b509d51d0c4cdc7 |
completed | May 11, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_6a01531a3a4c8190ac8cb040cc36e96b |
completed | May 11, 2026, 3:55 a.m. |
Created at: April 28, 2026, 9:42 a.m.