Triple
T36152263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brad Pitt as Jerry Welbach |
E1045620
|
entity |
| Predicate | notablePropInPlot |
P112925
|
FINISHED |
| Object | cursed antique pistol |
—
|
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: cursed antique pistol | Statement: [Brad Pitt as Jerry Welbach, notablePropInPlot, cursed antique pistol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePropInPlot Context triple: [Brad Pitt as Jerry Welbach, notablePropInPlot, cursed antique pistol]
-
A.
notableWorkInPlot
Indicates that a work is prominently featured or plays a significant role within the plot of another work.
-
B.
notableFeatureInStory
chosen
Indicates that a particular feature, element, or characteristic plays a significant or prominent role within a story.
-
C.
notablePropInteraction
Indicates a significant or noteworthy interaction or relationship occurring between the specified entities.
-
D.
hasNotableTraitInPlot
Indicates that a character or entity possesses a distinctive trait that plays a significant role within the narrative or plot.
-
E.
notablePropertyCluster
Indicates that multiple notable properties are grouped together as a coherent cluster or set associated with an entity.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.