Triple
T18482664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Got Me Going |
E451599
|
entity |
| Predicate | followsSingleYear |
P66026
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Got Me Going, followsSingleYear, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsSingleYear Context triple: [Got Me Going, followsSingleYear, 2007]
-
A.
followsSingleReleaseYear
chosen
Indicates that one entity is released in the year immediately following the release year of another single.
-
B.
focusesOnYears
Indicates that something is primarily concerned with or directed toward specific years or time periods.
-
C.
visitYear
Indicates the specific year in which a visit or visitation event took place.
-
D.
observesAllYear
Indicates that the observing entity continuously observes or monitors the target entity throughout the entire year without interruption.
-
E.
hasPartInYear
Indicates that something includes or contains a specific part, component, or segment that is associated with a particular year.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d49a1881908cc2ad6132953c96 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.