Triple
T3016784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gosford Park |
E82353
|
entity |
| Predicate | hasMurderMysteryElement |
P21752
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gosford Park, hasMurderMysteryElement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMurderMysteryElement Context triple: [Gosford Park, hasMurderMysteryElement, yes]
-
A.
hasMystery
chosen
Indicates that one entity possesses, contains, or is associated with something unknown, secret, or unexplained in relation to another entity.
-
B.
mysterySet
Indicates that an entity belongs to a collection or group whose nature, contents, or defining criteria are unknown or intentionally unspecified.
-
C.
hasEnigmaticCharacter
Indicates that something possesses a mysterious, puzzling, or difficult-to-interpret quality or nature.
-
D.
thirdMystery
Indicates a relationship where an entity is associated with the third mystery in a defined ordered set of mysteries (such as stages, secrets, or thematic elements).
-
E.
fourthMystery
Indicates the relationship of being the fourth mystery in an ordered sequence of mysteries.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a6c56708190b7d8d08bca727cc1 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.