Triple
T5479158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IKEv2 |
E123427
|
entity |
| Predicate | firstStandardizedInYear |
P7939
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [IKEv2, firstStandardizedInYear, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstStandardizedInYear Context triple: [IKEv2, firstStandardizedInYear, 2005]
-
A.
firstStandardPublicationYear
Indicates the year in which an entity’s work was first formally published according to a recognized standard or official publication record.
-
B.
firstStandardized
Indicates that an entity is the earliest or primary instance to which a standard or uniform specification has been first applied among comparable entities.
-
C.
goldStandardAdoptionYear
Indicates the year in which a particular gold standard was officially adopted or implemented.
-
D.
standardizedInYear
chosen
Indicates the specific year in which something was formally standardized or adopted as a standard.
-
E.
firstReportedYear
Indicates the year in which something was initially reported, documented, or made known for the first time.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.