Triple
T10212792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chess |
E242370
|
entity |
| Predicate | notableLyricTheme |
P4921
|
FINISHED |
| Object | individual versus state |
—
|
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: individual versus state | Statement: [Chess, notableLyricTheme, individual versus state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLyricTheme Context triple: [Chess, notableLyricTheme, individual versus state]
-
A.
notableLyricReference
Indicates that one entity contains a significant or well-known reference to the lyrics of another entity (such as a song or musical work).
-
B.
notableTheme
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
-
C.
hasLyricalTheme
chosen
Indicates that one entity (typically a creative work) features or is characterized by a particular lyrical subject, topic, or theme.
-
D.
notableSongCharacteristic
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
E.
notableChorus
Indicates that an entity is recognized for having a particularly prominent or distinguished chorus section.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa23bce881909b5deac612ec22cb |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:03 a.m.