Triple
T29408999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorkerGlobalScope |
E745843
|
entity |
| Predicate | runsIndependentlyOf |
P129313
|
FINISHED |
| Object | Window |
—
|
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: Window | Statement: [WorkerGlobalScope, runsIndependentlyOf, Window]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsIndependentlyOf Context triple: [WorkerGlobalScope, runsIndependentlyOf, Window]
-
A.
worksIndependentlyOf
chosen
Indicates that one entity performs its function or activity without relying on, being influenced by, or requiring coordination with another entity.
-
B.
organizedIndependentlyOf
Indicates that an entity was organized or formed without direction, control, or coordination from another specified entity.
-
C.
runsVia
Indicates that a process, operation, or connection is executed, routed, or carried out through a specified intermediate channel, path, or mechanism.
-
D.
maintainedIndependentlyFrom
Indicates that one entity continues to exist, operate, or be managed without reliance on or integration with another specified entity.
-
E.
runsFrom
Indicates that one entity flees or escapes away from 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_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. |
Created at: April 28, 2026, 2:55 p.m.