Triple
T5023364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Willis |
E112909
|
entity |
| Predicate | notableGenrePeriod |
P561
|
FINISHED |
| Object | disco era of the late 1970s |
—
|
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: disco era of the late 1970s | Statement: [Victor Willis, notableGenrePeriod, disco era of the late 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGenrePeriod Context triple: [Victor Willis, notableGenrePeriod, disco era of the late 1970s]
-
A.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
B.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
C.
historicallyImportantGenre
Indicates that the subject genre has played a significant and influential role in history or cultural development.
-
D.
notableCategory
Indicates that an entity is recognized as notable or significant within a particular category or classification.
-
E.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73670578819099a56112950708a8 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.