Triple
T15345052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stereolab |
E366893
|
entity |
| Predicate | hiatusStartYear |
P10338
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Stereolab, hiatusStartYear, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiatusStartYear Context triple: [Stereolab, hiatusStartYear, 2009]
-
A.
beganInYear
chosen
Indicates that an event, process, or state started in a specific calendar year.
-
B.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
C.
laterTypeStartYear
Indicates that the starting year of one type or classification occurs later in time than the starting year of another type or classification.
-
D.
typicalStartYear
Indicates the year in which something (such as an event, activity, or process) usually or customarily begins.
-
E.
recordStartYear
Indicates the calendar year in which a particular record, entry, or data instance first began or was created.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e163a3c8190ab933411372c1573 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.