Triple
T29409061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SyncManager |
E745844
|
entity |
| Predicate | eventDispatchedTo |
P83867
|
FINISHED |
| Object | ServiceWorkerGlobalScope |
—
|
NE NERFINISHED |
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: ServiceWorkerGlobalScope | Statement: [SyncManager, eventDispatchedTo, ServiceWorkerGlobalScope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDispatchedTo Context triple: [SyncManager, eventDispatchedTo, ServiceWorkerGlobalScope]
-
A.
eventCommanded
Indicates that one entity issued an order or directive for another entity to carry out a specific event or action.
-
B.
eventBroadcastOn
Indicates that an event is transmitted or made available through a particular broadcast channel, medium, or platform.
-
C.
eventTarget
chosen
Indicates that an event is directed toward, affects, or is intended for a particular target entity.
-
D.
displacementEvent
Indicates an event in which an entity is moved or shifted from its original position or location to a different one.
-
E.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 2:56 p.m.