Triple
T30757830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The River Tour |
E783137
|
entity |
| Predicate | notableAudienceReaction |
P35855
|
FINISHED |
| Object | strong fan following |
—
|
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: strong fan following | Statement: [The River Tour, notableAudienceReaction, strong fan following]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAudienceReaction Context triple: [The River Tour, notableAudienceReaction, strong fan following]
-
A.
notableAudience
Indicates that an entity is especially well-known, relevant, or targeted among a particular audience or group of people.
-
B.
notableReception
chosen
Indicates that something has received significant attention, recognition, or response from audiences, critics, or the public.
-
C.
causedReaction
Indicates that one entity’s action or state brought about a specific reaction or response in another entity.
-
D.
notableImpression
Indicates that one entity has made a significant or memorable impact on another entity.
-
E.
notableVolume
Indicates that an entity is a significant or well-known volume (such as a book or written work) associated with another entity.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:39 p.m.