Triple
T34238702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAV |
E878401
|
entity |
| Predicate | servesMilitary |
P65983
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SAV, servesMilitary, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesMilitary Context triple: [SAV, servesMilitary, yes]
-
A.
hasMilitaryStatus
chosen
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
-
B.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
C.
hadMilitaryServiceFrom
Indicates that an entity performed or was engaged in military service starting from a specified point in time.
-
D.
hasMilitaryBranch
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
E.
usedByBranchOfMilitary
Indicates that something is utilized or operated by a specific branch of a country's military forces.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: May 1, 2026, 1:56 a.m.