Triple
T19665759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sugar Mountain |
E472193
|
entity |
| Predicate | performedLiveSinceDecade |
P136876
|
FINISHED |
| Object | 1960s |
—
|
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 | Statement: [Sugar Mountain, performedLiveSinceDecade, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedLiveSinceDecade Context triple: [Sugar Mountain, performedLiveSinceDecade, 1960s]
-
A.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
B.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
-
C.
hasLivePerformancesRecorded
Indicates that live performances of an entity (such as a work, event, or artist) have been captured and stored as recordings.
-
D.
hasPerformedLiveIn
Indicates that an entity has given a live performance in a specified location or venue.
-
E.
hasLivePerformanceStatus
Indicates whether an entity’s live performance is occurring, scheduled, completed, or otherwise characterized by a specific performance status.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416857c88190acb3adbf3e585fe5 |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.