Triple
T33799375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noël Coward as Mr. Bridger |
E866170
|
entity |
| Predicate | plansHeistFrom |
P126716
|
FINISHED |
| Object | prison |
—
|
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: prison | Statement: [Noël Coward as Mr. Bridger, plansHeistFrom, prison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansHeistFrom Context triple: [Noël Coward as Mr. Bridger, plansHeistFrom, prison]
-
A.
plansRobberyIn
chosen
Indicates that an entity is preparing or organizing to commit a robbery within a specified location or jurisdiction.
-
B.
plansToMurder
Indicates that one entity intends and has formed a plan to unlawfully kill another entity.
-
C.
plansMurdersToMatch
Indicates that an entity devises murders so that they correspond to or align with another pattern, plan, or set of criteria.
-
D.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
E.
planningSkill
Indicates the degree to which an entity is capable of effectively organizing, sequencing, and coordinating actions or resources to achieve goals.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:46 a.m.