Triple
T7949933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phenomenon |
E184587
|
entity |
| Predicate | notablePeriodInArtistCareer |
P30618
|
FINISHED |
| Object | late 1990s |
—
|
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: late 1990s | Statement: [Phenomenon, notablePeriodInArtistCareer, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePeriodInArtistCareer Context triple: [Phenomenon, notablePeriodInArtistCareer, late 1990s]
-
A.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
B.
notableWorkYear
Indicates the year in which a notable work associated with an entity was created, released, or achieved prominence.
-
C.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
D.
timeInArtistCareer
chosen
Indicates the point or period within an artist’s professional career at which a given event, work, or activity occurs.
-
E.
notableEventInCareer
Indicates that a particular event is a significant or defining occurrence within an entity’s professional career.
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2d09a4819097aa49e29a5426ec |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae9361bc48190886b7681e563d46b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:10 p.m.