Triple
T18724894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WARC |
E457874
|
entity |
| Predicate | latestRevisionYear |
P45458
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [WARC, latestRevisionYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestRevisionYear Context triple: [WARC, latestRevisionYear, 2017]
-
A.
latestVersionYear
Indicates the calendar year in which the most recent version of an entity (such as a product, document, or software) was released or became available.
-
B.
finalVersionYear
Indicates the year in which the final or last version of something was completed, released, or became definitive.
-
C.
mostRecentEditionYear
Indicates the calendar year in which the most recently released edition of an entity (such as a work, product, or publication) was published or made available.
-
D.
dateRevisionYear
chosen
Indicates the calendar year in which a particular date entry or record was revised or updated.
-
E.
majorRevisionYear
Indicates the year in which a significant or primary revision of something (such as a work, document, or standard) was made.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d72d2c4819080b0d31860976b5e |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:50 a.m.