Triple
T9797574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World War II veterans |
E237755
|
entity |
| Predicate | servedInBranch |
P253
|
FINISHED |
| Object | army |
—
|
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: army | Statement: [World War II veterans, servedInBranch, army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedInBranch Context triple: [World War II veterans, servedInBranch, army]
-
A.
servedInRole
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
-
B.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
C.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
-
D.
worksAtBranch
Indicates that an individual is employed at and performs their job duties at a specific branch of an organization.
-
E.
hasMilitaryBranch
chosen
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda6264160819080da4805b213753f |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.