Triple
T13792853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trauma |
E331440
|
entity |
| Predicate | mainGenreRegion |
P111298
|
FINISHED |
| Object | West Coast |
—
|
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: West Coast | Statement: [Trauma, mainGenreRegion, West Coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGenreRegion Context triple: [Trauma, mainGenreRegion, West Coast]
-
A.
musicGenreRegion
chosen
Indicates the association between a music genre and the geographic region where it originates, is most prevalent, or is culturally significant.
-
B.
hasGenreOrigin
Indicates that a genre originates from, or has its roots in, a particular source, place, culture, or tradition.
-
C.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
D.
commonGenre
Indicates that two entities share at least one genre in common.
-
E.
genreRestriction
Indicates that there is a limitation or constraint on which genres are allowed or applicable in a given context.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0258a1408190a837d17c6d6a2bd4 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.