Triple
T18048910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada RPM Top Singles |
E431873
|
entity |
| Predicate | startTime_precision |
P119939
|
FINISHED |
| Object | year |
—
|
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: year | Statement: [Canada RPM Top Singles, startTime_precision, year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTime_precision Context triple: [Canada RPM Top Singles, startTime_precision, year]
-
A.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
B.
startTimeDetail
Indicates the specific, often more granular or formatted, time at which an event or action begins.
-
C.
timeGranularity
chosen
Indicates the level of temporal detail or precision at which an event, measurement, or relationship is defined (e.g., seconds, days, months).
-
D.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
-
E.
positionStartTime
Indicates the time at which a position, role, or placement begins.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff4a6e08190a5ca8d191aa7f0ae |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.