Triple
T34457751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariano Matamoros |
E884546
|
entity |
| Predicate | yearOfMilitaryServiceEnd |
P19195
|
FINISHED |
| Object | 1814 |
—
|
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: 1814 | Statement: [Mariano Matamoros, yearOfMilitaryServiceEnd, 1814]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfMilitaryServiceEnd Context triple: [Mariano Matamoros, yearOfMilitaryServiceEnd, 1814]
-
A.
hasMilitaryServiceEnd
chosen
Indicates the date or point in time at which an entity’s period of military service concludes.
-
B.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
-
C.
militaryServicePeriod
Indicates the span of time during which an entity serves or has served in a military capacity.
-
D.
militarySupportEndYear
Indicates the year in which a previously provided military support relationship or assistance comes to an end.
-
E.
retiredFromUSMilitary
Indicates that an individual previously served in the United States military and has formally ended their military career or service.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 1, 2026, 2 a.m.