Triple
T33237370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tim Gutterson |
E850864
|
entity |
| Predicate | branchOfMilitaryService |
P253
|
FINISHED |
| Object | United States Army Rangers |
—
|
NE NERFINISHED |
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: United States Army Rangers | Statement: [Tim Gutterson, branchOfMilitaryService, United States Army Rangers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchOfMilitaryService Context triple: [Tim Gutterson, branchOfMilitaryService, United States Army Rangers]
-
A.
hasMilitaryBranch
chosen
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
B.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
-
C.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
-
D.
militaryBranchDomain
Indicates that one entity serves as the military branch or armed forces component associated with the domain, jurisdiction, or organizational scope of another entity.
-
E.
militaryBranchOfGovernment
Indicates that a military organization functions as an official branch or component of a government.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:31 a.m.