Triple
T33509474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larry Linville |
E858199
|
entity |
| Predicate | portrayedBranchOfService |
P170341
|
FINISHED |
| Object | U.S. Army |
—
|
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: U.S. Army | Statement: [Larry Linville, portrayedBranchOfService, U.S. Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedBranchOfService Context triple: [Larry Linville, portrayedBranchOfService, U.S. Army]
-
A.
portrayedMilitaryRole
chosen
Indicates that one entity depicted or acted in a military role associated with another entity, such as in a film, show, or performance.
-
B.
fictionalServiceBranch
Indicates that an entity is associated with a military or organizational service branch that exists only within a fictional or imaginary context.
-
C.
namedForPersonMilitaryBranch
Indicates that a military branch is named in honor of or after a specific person.
-
D.
hasMilitaryBranch
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
E.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: May 1, 2026, 1:38 a.m.