Triple
T213950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | military payment certificates |
E4776
|
entity |
| Predicate | lastSeriesIssued |
P8538
|
FINISHED |
| Object | Series 692 |
—
|
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: Series 692 | Statement: [military payment certificates, lastSeriesIssued, Series 692]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastSeriesIssued Context triple: [military payment certificates, lastSeriesIssued, Series 692]
-
A.
lastAwarded
Indicates the most recent time or instance at which an entity received a particular award.
-
B.
currentSeriesIntroduced
Indicates that an entity was first introduced or appeared in the currently ongoing series or installment of a work.
-
C.
lastLifetimeEditionYear
Indicates the year in which the most recent lifetime edition of an entity (such as a work or product) was issued or became available.
-
D.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
E.
beganOfficialNumberingWith
Indicates that an entity started its formal or official numbering sequence with a specified initial number or identifier.
- F. None of above. chosen
Provenance (4 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c32ae208190a03d504ef43ea659 |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b509400819093a6c1a1bac861e3 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25c036b54819090a101c4cbdbcff7 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.