Triple
T19980326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curracloe Beach |
E493799
|
entity |
| Predicate | usedForSceneType |
P133189
|
FINISHED |
| Object | D-Day landing scenes |
—
|
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: D-Day landing scenes | Statement: [Curracloe Beach, usedForSceneType, D-Day landing scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForSceneType Context triple: [Curracloe Beach, usedForSceneType, D-Day landing scenes]
-
A.
performedInSceneType
Indicates that an action or event was carried out within a scene of a specified type or category.
-
B.
underscoresSceneType
Indicates that the subject emphasizes or highlights the type or category of a scene associated with the object.
-
C.
supportsScene
chosen
Indicates that one entity provides the necessary structure, resources, or compatibility for a particular scene or scenario to function or be presented.
-
D.
filmSceneType
Indicates the type or category of a scene within a film, such as its narrative function, style, or setting.
-
E.
usesStageType
Indicates that one entity employs or operates with a particular type or category of stage.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d12d968819081e315ec4585cd9f |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:27 p.m.