Triple
T25535656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayday live support |
E640031
|
entity |
| Predicate | supportsInteractionType |
P96076
|
FINISHED |
| Object | live video assistance |
—
|
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: live video assistance | Statement: [Mayday live support, supportsInteractionType, live video assistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInteractionType Context triple: [Mayday live support, supportsInteractionType, live video assistance]
-
A.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
B.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
usedInteractionType
chosen
Indicates the specific type or category of interaction that was used between the related entities.
-
D.
appliesToInteraction
Indicates that something (such as a rule, condition, or property) is relevant to or governs a specific interaction between entities.
-
E.
supportsPermissionType
Indicates that one entity is capable of handling, allowing, or being configured with a specified type of permission.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 21, 2026, 3:22 p.m.