Triple
T31166200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Look Through Any Window |
E794474
|
entity |
| Predicate | hasOriginScene |
P167035
|
FINISHED |
| Object | British pop scene |
—
|
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: British pop scene | Statement: [Look Through Any Window, hasOriginScene, British pop scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginScene Context triple: [Look Through Any Window, hasOriginScene, British pop scene]
-
A.
originatedScene
chosen
Indicates that one entity is the original source or starting point scene from which another scene, event, or representation is derived.
-
B.
hasInfluenceFromScene
Indicates that something is affected, shaped, or guided by the characteristics or context of a particular scene.
-
C.
hasSceneLocation
Indicates that a scene or event takes place at, or is set in, a specific location.
-
D.
containsScene
Indicates that one entity (typically a media item or narrative work) includes or features a particular scene as part of its content.
-
E.
hasStagedSceneAs
Indicates that one entity has arranged, directed, or presented another entity in a particular scene or setting, typically for performance, display, or representation.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 29, 2026, 9:07 p.m.