Triple
T34352141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Hunsaker |
E881609
|
entity |
| Predicate | militaryComradeOf |
P102772
|
FINISHED |
| Object | Roger Murtaugh |
—
|
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: Roger Murtaugh | Statement: [Michael Hunsaker, militaryComradeOf, Roger Murtaugh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryComradeOf Context triple: [Michael Hunsaker, militaryComradeOf, Roger Murtaugh]
-
A.
unitComrades
chosen
Indicates that two or more entities serve or operate together as comrades within the same unit or group.
-
B.
brotherOrAlly
Indicates a relationship where one entity is either a brother of, or an allied supporter/partner to, another entity.
-
C.
numberOfBrothersInServiceTogether
Indicates the count of brothers who are serving simultaneously in the same context (e.g., organization, unit, or service).
-
D.
isReservistComponentOf
Indicates that an individual serves as a reservist member within a specified larger military or organizational component.
-
E.
isMilitaryStaffOf
Indicates that one entity serves as military personnel working for, or assigned to, another entity (such as an organization, unit, or individual).
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:58 a.m.