Triple
T209895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B. B. King |
E4690
|
entity |
| Predicate | touringActivity |
P9124
|
FINISHED |
| Object | performed extensively worldwide |
—
|
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: performed extensively worldwide | Statement: [B. B. King, touringActivity, performed extensively worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touringActivity Context triple: [B. B. King, touringActivity, performed extensively worldwide]
-
A.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
B.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
C.
notableTour
Indicates that an entity is recognized for having a significant or well-known tour associated with it.
-
D.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
E.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b4f71b88190866c8262922ae204 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25d3463648190ac716d7475378536 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.