Triple
T22865791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten Minute Warning |
E567048
|
entity |
| Predicate | hasLocalScene |
P84945
|
FINISHED |
| Object | Seattle punk 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: Seattle punk scene | Statement: [Ten Minute Warning, hasLocalScene, Seattle punk scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalScene Context triple: [Ten Minute Warning, hasLocalScene, Seattle punk scene]
-
A.
hasSceneLocation
Indicates that a scene or event takes place at, or is set in, a specific location.
-
B.
hasRegionalScene
chosen
Indicates that something possesses or is associated with a specific regional scene, such as a localized cultural, artistic, or social milieu.
-
C.
containsScene
Indicates that one entity (typically a media item or narrative work) includes or features a particular scene as part of its content.
-
D.
hasLocalMedia
Indicates that an entity is associated with media content that is stored or available locally rather than from a remote source.
-
E.
hasLastSceneWith
Indicates that two entities share the same final scene or appearance together within a work or sequence.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f00f21081909b771610549c5757 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.