Triple
T3305135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Infrastructure Protection Plan |
E69429
|
entity |
| Predicate | updatedVersionPublicationYear |
P45458
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [National Infrastructure Protection Plan, updatedVersionPublicationYear, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedVersionPublicationYear Context triple: [National Infrastructure Protection Plan, updatedVersionPublicationYear, 2009]
-
A.
coverVersionReleaseYear
Indicates the year in which a particular cover version of an original work was released.
-
B.
lastPublicationYear
Indicates the year in which an entity’s most recent publication was released.
-
C.
EPReleaseYear
Indicates the calendar year in which an EP (extended play recording) was officially released.
-
D.
ARVersionAnnouncementYear
Indicates the year in which a specific version of an augmented reality (AR) product or system was officially announced.
-
E.
dateRevisionYear
chosen
Indicates the calendar year in which a particular date entry or record was revised or updated.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c8179081908a2595d1fdb7560a |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.