Triple
T29011654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ShowDialogItem |
E736580
|
entity |
| Predicate | mayControl |
P30853
|
FINISHED |
| Object | dialog modality |
—
|
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: dialog modality | Statement: [ShowDialogItem, mayControl, dialog modality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayControl Context triple: [ShowDialogItem, mayControl, dialog modality]
-
A.
canControl
chosen
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
B.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
C.
mayRuleOver
Indicates that one entity has the potential or permission to exercise authority or governance over another entity.
-
D.
mayDirect
Indicates that one entity has the permission or authority to direct, manage, or oversee the actions or operations of another entity.
-
E.
mayConduct
Indicates that one entity is permitted or authorized to carry out, perform, or execute a particular action, process, or operation on or with another entity.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fdc78c481908836151d03329ae7 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:42 a.m.