Triple
T5163818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beau Geste |
E116499
|
entity |
| Predicate | hasMotiveForPlot |
P53895
|
FINISHED |
| Object | the theft of a valuable sapphire |
—
|
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: the theft of a valuable sapphire | Statement: [Beau Geste, hasMotiveForPlot, the theft of a valuable sapphire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotiveForPlot Context triple: [Beau Geste, hasMotiveForPlot, the theft of a valuable sapphire]
-
A.
hasMotiveElement
Indicates that one entity includes, specifies, or is characterized by a particular motive-related component or factor in a broader relationship or action.
-
B.
reasonForMurder
Indicates the motive or underlying cause that led someone to commit a murder.
-
C.
hasMystery
Indicates that one entity possesses, contains, or is associated with something unknown, secret, or unexplained in relation to another entity.
-
D.
hasMainPlotElement
chosen
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
-
E.
hasEnigmaticCharacter
Indicates that something possesses a mysterious, puzzling, or difficult-to-interpret quality or nature.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7927a348819082ad531955cdf30d |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.