Triple
T29664804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do You Feel Like We Do |
E750498
|
entity |
| Predicate | liveVersionType |
P168164
|
FINISHED |
| Object | extended jam |
—
|
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: extended jam | Statement: [Do You Feel Like We Do, liveVersionType, extended jam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveVersionType Context triple: [Do You Feel Like We Do, liveVersionType, extended jam]
-
A.
liveVersionTitle
Indicates the title associated with the live or currently active version of something (such as a document, release, or piece of content).
-
B.
liveVersionReleasedOn
Indicates the date or time when a live version of something (such as a product, feature, or content) is officially released or made available.
-
C.
isLiveVersion
Indicates that one entity is the current, active, or publicly available version of another entity.
-
D.
liveVersionRecordedAt
Indicates that a live version of something (such as a performance or recording) was recorded at a specific place or event.
-
E.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 28, 2026, 7 p.m.