Triple
T4950865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raiders March |
E111163
|
entity |
| Predicate | hasSecondaryMotif |
P31989
|
FINISHED |
| Object | lyrical love theme |
—
|
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: lyrical love theme | Statement: [Raiders March, hasSecondaryMotif, lyrical love theme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryMotif Context triple: [Raiders March, hasSecondaryMotif, lyrical love theme]
-
A.
hasSecondaryBase
Indicates that an entity possesses or is associated with a secondary or additional base, distinct from its primary base.
-
B.
hasSecondarySubject
Indicates that an entity is associated with an additional, non-primary subject in a given context or relationship.
-
C.
hasSecondaryPeak
Indicates that an entity exhibits an additional, smaller peak or maximum beyond its primary peak in its profile or behavior.
-
D.
hasSecondaryCore
Indicates that an entity possesses an additional, subordinate core component alongside its primary core.
-
E.
usesMotifsFrom
chosen
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
- 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.