Triple
T31756041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Go On |
E810557
|
entity |
| Predicate | inspiredEmotion |
P182268
|
FINISHED |
| Object | uplift |
—
|
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: uplift | Statement: [We Go On, inspiredEmotion, uplift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredEmotion Context triple: [We Go On, inspiredEmotion, uplift]
-
A.
inspiration
Indicates that one entity serves as a motivating or creative influence that stimulates ideas, actions, or feelings in another entity.
-
B.
inspiredDedicationOf
Indicates that one entity’s dedication, commitment, or devoted effort is motivated, sparked, or strengthened by another entity.
-
C.
hasInspired
Indicates that one entity has served as a source of motivation, creativity, or influence leading to ideas, actions, or works in another entity.
-
D.
inspiredField
Indicates that one entity served as a source of inspiration or influence for the development, direction, or characteristics of a particular field or domain.
-
E.
inspiredSong
Indicates that one entity (such as an event, person, or work) served as the creative inspiration or motivating influence for the creation of a particular song.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 30, 2026, 11:29 p.m.