Triple
T10328949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web workers |
E242829
|
entity |
| Predicate | lifecycleControlledBy |
P85670
|
FINISHED |
| Object | Main thread |
—
|
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: Main thread | Statement: [Web workers, lifecycleControlledBy, Main thread]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifecycleControlledBy Context triple: [Web workers, lifecycleControlledBy, Main thread]
-
A.
lifecycleStatus
Indicates the current phase or condition of an entity within its overall lifecycle or progression from creation to termination.
-
B.
lifecycleType
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
-
C.
lifecycleModel
chosen
Indicates that one entity defines or follows the structured sequence of phases or stages governing the development, use, and retirement of another entity.
-
D.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
E.
versionControlledBy
Indicates that an item (such as a file, document, or resource) is managed and tracked under the change history of a specific version control system or repository.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.