Triple
T166340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 830 |
E3022
|
entity |
| Predicate | yearOfCurrentEdition |
P4001
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [IEEE 830, yearOfCurrentEdition, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfCurrentEdition Context triple: [IEEE 830, yearOfCurrentEdition, 1998]
-
A.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
B.
lastLifetimeEditionYear
chosen
Indicates the year in which the most recent lifetime edition of an entity (such as a work or product) was issued or became available.
-
C.
edition
Indicates that one entity is a specific version, issue, or release of another (typically a work such as a book, journal, or software).
-
D.
publicationYear
Indicates the specific calendar year in which a work was formally published or released.
-
E.
nextEdition
Indicates that one entity is the immediate subsequent edition or version that follows another in a sequence.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a25883ac8481909616b2179561bd98 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25664ba8081908ac298511a9fc5ba |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.