Triple
T14395261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YouTrack |
E356932
|
entity |
| Predicate | supportsNotificationChannel |
P53673
|
FINISHED |
| Object |
—
|
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: email | Statement: [YouTrack, supportsNotificationChannel, email]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNotificationChannel Context triple: [YouTrack, supportsNotificationChannel, email]
-
A.
supportsPushNotifications
Indicates that an entity is capable of sending or handling push notifications for another entity or user.
-
B.
supportsChannels
chosen
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
-
C.
requiresNotification
Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
-
D.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de902d114881908a8f3c01b3c6d309 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.