Triple
T5147658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Frustrators |
E116112
|
entity |
| Predicate | activeInScene |
P61824
|
FINISHED |
| Object | California punk rock 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: California punk rock scene | Statement: [The Frustrators, activeInScene, California punk rock scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInScene Context triple: [The Frustrators, activeInScene, California punk rock scene]
-
A.
activeInEvent
Indicates that an entity participates in or is involved in carrying out actions within a particular event.
-
B.
hasInfluenceFromScene
Indicates that something is affected, shaped, or guided by the characteristics or context of a particular scene.
-
C.
activeInFieldFrom
Indicates that an entity is professionally or actively engaged in a particular field starting from a specified point in time.
-
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.
isPotentiallyActive
Indicates that an entity has the capacity or conditions to become active, but is not necessarily active at the present moment.
- F. None of above. chosen
Provenance (4 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78d7f4d081908d59adcd86f52f1d |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77ae2f10819098bb8939106e1281 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:43 p.m.