Triple
T29409002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorkerGlobalScope |
E745843
|
entity |
| Predicate | isGlobalObjectFor |
P166754
|
FINISHED |
| Object | DedicatedWorkerGlobalScope |
—
|
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: DedicatedWorkerGlobalScope | Statement: [WorkerGlobalScope, isGlobalObjectFor, DedicatedWorkerGlobalScope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGlobalObjectFor Context triple: [WorkerGlobalScope, isGlobalObjectFor, DedicatedWorkerGlobalScope]
-
A.
isGlobalScope
Indicates that something exists or applies at the global scope, rather than being limited to a local or nested context.
-
B.
isClassicalObjectIn
Indicates that a classical (non-quantum) object is located within or belongs to a specified region, context, or system.
-
C.
hasGlobalOwner
Indicates that an entity is owned or controlled by a global-level owner, rather than a local or specific one.
-
D.
isOrdinaryOf
Indicates that one entity is the standard, non-special, or typical instance or form of another entity.
-
E.
hasGlobalHost
Indicates that an entity is associated with or served by a host that is accessible or applicable at a global (system-wide or worldwide) level.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a36aaec8190b5914c698ba12ee1 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:55 p.m.