Triple
T18666981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100 Yard Dash |
E456358
|
entity |
| Predicate | hasEraInfluence |
P132209
|
FINISHED |
| Object | 1960s soul |
—
|
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: 1960s soul | Statement: [100 Yard Dash, hasEraInfluence, 1960s soul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEraInfluence Context triple: [100 Yard Dash, hasEraInfluence, 1960s soul]
-
A.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
B.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
C.
usedDuringEraOf
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
-
D.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
E.
playedWithEra
Indicates that an entity performed or was active during a specified historical or stylistic era.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556ad88b481908bd008d469e878fd |
completed | April 19, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.