Triple
T12425539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rambo film series |
E296888
|
entity |
| Predicate | protagonistConflict |
P20969
|
FINISHED |
| Object | Vietnam War veteran |
—
|
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: Vietnam War veteran | Statement: [Rambo film series, protagonistConflict, Vietnam War veteran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistConflict Context triple: [Rambo film series, protagonistConflict, Vietnam War veteran]
-
A.
storyConflict
Indicates a relationship where a story contains or centers around a central problem, opposition, or tension that drives its plot.
-
B.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
C.
protagonistAction
Indicates that the referenced entity performs the central or primary action associated with the main character in a narrative or scenario.
-
D.
protagonistField
Indicates that the subject is the main or central character (protagonist) within the specified narrative or context.
-
E.
protagonistType
chosen
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.