Triple
T29034819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces of Armenia |
E737828
|
entity |
| Predicate | standardServiceAge |
P176732
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [Armed Forces of Armenia, standardServiceAge, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardServiceAge Context triple: [Armed Forces of Armenia, standardServiceAge, 18]
-
A.
serviceAge
Indicates the length of time an entity has been in service or actively performing its role.
-
B.
standardServiceRoundOf
Indicates that one entity is the standard or typical service round associated with another entity (such as a process, schedule, or service context).
-
C.
typicalTimeInServiceToAttain
Indicates the usual duration of service required for an entity to reach or attain a specified status, level, or condition.
-
D.
typicalAgingTime
Indicates the usual duration required for something to age or mature under normal conditions.
-
E.
serviceEra
Indicates the historical period or era during which a service, role, or duty was performed.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 28, 2026, 9:57 a.m.