Triple
T9949099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian I Corps |
E195282
|
entity |
| Predicate | dateInService |
P61845
|
FINISHED |
| Object | 1815 |
—
|
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: 1815 | Statement: [Prussian I Corps, dateInService, 1815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateInService Context triple: [Prussian I Corps, dateInService, 1815]
-
A.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
-
B.
serviceEntryDate
chosen
Indicates the date on which a service or duty officially began or was first entered into the record.
-
C.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
D.
yearOfUse
Indicates the specific year during which something was in use or actively utilized.
-
E.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb659307c81908279adb641ceef86 |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.