Triple
T21082315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Next Generation Identification |
E519398
|
entity |
| Predicate | startOfDeployment |
P11880
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Next Generation Identification, startOfDeployment, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfDeployment Context triple: [Next Generation Identification, startOfDeployment, 2008]
-
A.
deploymentTime
chosen
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
B.
firstLargeDeployment
Indicates that this is the initial instance in which something is deployed at a large or significant scale.
-
C.
firstDeploymentContext
Indicates the context, environment, or situation in which something (typically a system, product, or capability) is initially deployed or put into operational use.
-
D.
implementationStart
Indicates the point in time or event at which the implementation of something (such as a plan, system, or project) begins.
-
E.
startDuring
Indicates that one event or interval begins at some point strictly within the duration of another event or interval, but not at its start.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702dcbf9c81908e4cc016eb21bbbc |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.