Triple
T4950864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raiders March |
E111163
|
entity |
| Predicate | hasMainMotif |
P2366
|
FINISHED |
| Object | heroic brass fanfare |
—
|
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: heroic brass fanfare | Statement: [Raiders March, hasMainMotif, heroic brass fanfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainMotif Context triple: [Raiders March, hasMainMotif, heroic brass fanfare]
-
A.
primaryMotif
chosen
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
B.
featuresMotif
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
-
C.
usesMotifsFrom
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
-
D.
hasTitleMotif
Indicates that a work’s title prominently features or reflects a recurring motif or central thematic element within the work.
-
E.
hasMainOrgan
Indicates that an entity possesses a primary or principal organ that plays a central role in its biological or functional system.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b561ec81908083225269222e96 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.