Triple
T34457750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariano Matamoros |
E884546
|
entity |
| Predicate | yearOfMilitaryServiceStart |
P19194
|
FINISHED |
| Object | 1811 |
—
|
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: 1811 | Statement: [Mariano Matamoros, yearOfMilitaryServiceStart, 1811]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfMilitaryServiceStart Context triple: [Mariano Matamoros, yearOfMilitaryServiceStart, 1811]
-
A.
hasMilitaryServiceStart
chosen
Indicates the date or point in time when an entity’s period of military service began.
-
B.
militaryServicePeriod
Indicates the span of time during which an entity serves or has served in a military capacity.
-
C.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
-
D.
enlistmentYear
Indicates the year in which an entity formally joined or was enrolled into a service, organization, or group.
-
E.
dateCommissioned
Indicates the date on which something (such as a project, artwork, or equipment) was formally ordered, authorized, or put into official 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_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 1, 2026, 2 a.m.