Triple
T22814359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manifest V3 |
E565061
|
entity |
| Predicate | rolloutStartedIn |
P77313
|
FINISHED |
| Object | around 2021 |
—
|
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: around 2021 | Statement: [Manifest V3, rolloutStartedIn, around 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rolloutStartedIn Context triple: [Manifest V3, rolloutStartedIn, around 2021]
-
A.
rolloutDate
chosen
Indicates the date on which something (such as a product, feature, or policy) is first introduced or made available for general use.
-
B.
rollout
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.
rolloutLocation
Indicates the place or geographic area where a product, service, feature, or initiative is initially or progressively deployed.
-
D.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
E.
startedNear
Indicates that one event or action began close in time or space to another event or action.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d62b0ec8190ac22909192e8a876 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:33 p.m.