Triple
T29409042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorkerGlobalScope |
E745843
|
entity |
| Predicate | lifecycleBoundTo |
P94367
|
FINISHED |
| Object | worker lifetime |
—
|
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: worker lifetime | Statement: [WorkerGlobalScope, lifecycleBoundTo, worker lifetime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifecycleBoundTo Context triple: [WorkerGlobalScope, lifecycleBoundTo, worker lifetime]
-
A.
lifecycleTiedTo
chosen
Indicates that the existence, duration, or validity of one entity is dependent on and ends with the lifecycle of another entity.
-
B.
lifecycleBehavior
Indicates how an entity behaves, changes, or is managed over the course of its existence or lifecycle.
-
C.
lifecycleType
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
-
D.
lifecycleManagedBy
Indicates that the entire lifecycle of an entity (such as its creation, updates, and retirement) is overseen or controlled by another entity.
-
E.
designedForLifecycle
Indicates that something has been intentionally created or configured to support, align with, or optimize a particular lifecycle or set of lifecycle stages.
- 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_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:55 p.m.