Triple
T17721448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opal network |
E442345
|
entity |
| Predicate | fullRolloutCompleted |
P73878
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Opal network, fullRolloutCompleted, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullRolloutCompleted Context triple: [Opal network, fullRolloutCompleted, 2014]
-
A.
fullOpeningCompleted
Indicates that the action or process of fully opening something has been completed.
-
B.
rollout
chosen
Indicates the action of introducing or deploying something (such as a product, feature, or policy) from a limited or initial state to broader or full availability over time.
-
C.
fullyAppliedTo
Indicates that an action, function, or process has been completely and exhaustively applied to a target entity, with no remaining parameters or partial application.
-
D.
hasCompleted
Indicates that an entity has finished or successfully carried out a specified task, process, or activity.
-
E.
wentFullyOnline
Indicates that an entity transitioned from a non-online or partially online state to operating entirely online.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47486438c8190abe27eb4eb2c6fdf |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:07 a.m.