Triple
T25563841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Čermak |
E640782
|
entity |
| Predicate | activeYearsInMilitary |
P46479
|
FINISHED |
| Object | 1991–1995 |
—
|
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: 1991–1995 | Statement: [Ivan Čermak, activeYearsInMilitary, 1991–1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeYearsInMilitary Context triple: [Ivan Čermak, activeYearsInMilitary, 1991–1995]
-
A.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
-
B.
militaryServicePeriod
chosen
Indicates the span of time during which an entity serves or has served in a military capacity.
-
C.
serviceNumberOrYearsOfService
Indicates a relationship that specifies either an entity’s service identification number or the duration of time the entity has served.
-
D.
yearsMissedForMilitaryService
Indicates the number of years an entity did not participate in an activity or role due to serving in the military.
-
E.
activeYearsWith
Indicates the span of time during which an entity was actively engaged in a particular role, activity, or association with another entity.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8fa9fa0819098761026a7f9353d |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 3:48 p.m.