Triple
T4135412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taste the Feeling |
E85140
|
entity |
| Predicate | hasLocalizedVersions |
P32680
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Taste the Feeling, hasLocalizedVersions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalizedVersions Context triple: [Taste the Feeling, hasLocalizedVersions, yes]
-
A.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
-
B.
hasInternationalVersion
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
-
C.
hasRegionalVariationsIn
chosen
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
-
D.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
E.
hasLiveVersions
Indicates that an entity has one or more recorded or documented live-performance versions of itself.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.