Triple
T1287953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gold Rush |
E27477
|
entity |
| Predicate | famousScene |
P7326
|
FINISHED |
| Object | dinner roll dance |
—
|
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: dinner roll dance | Statement: [The Gold Rush, famousScene, dinner roll dance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousScene Context triple: [The Gold Rush, famousScene, dinner roll dance]
-
A.
notableScene
chosen
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
B.
filmLocationFor
Indicates a relationship where a specific place serves as the filming location for a particular film or production.
-
C.
notableCultImage
Indicates that an entity is associated with a significant or historically important religious or cultic image.
-
D.
isMostProminentIn
Indicates that an entity stands out as the most notable, influential, or dominant among comparable entities within a specified context or domain.
-
E.
notableCastFeature
Indicates that a cast member has a distinctive or noteworthy characteristic, role, or attribute that is especially significant in the context of the production.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d38d7c81908941edda9cac5d6a |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.