Triple
T7933718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rich Text Format |
E184240
|
entity |
| Predicate | latestSpecificationPublication |
P6757
|
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: [Rich Text Format, latestSpecificationPublication, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestSpecificationPublication Context triple: [Rich Text Format, latestSpecificationPublication, 2008]
-
A.
updatedSpecificationDate
chosen
Indicates the date on which a specification was last revised or brought up to date.
-
B.
latestMajorVersionPublisher
Indicates that the subject is the publisher responsible for releasing the most recent major version of the referenced entity.
-
C.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
D.
lastEdition
Indicates that one entity is the most recent or final edition/version within a series or sequence of editions.
-
E.
specificationStatus
Indicates the current approval or completion state of a specification within its lifecycle (e.g., draft, under review, finalized).
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aeb132c8190bea4906aaf51b869 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.