Triple
T16943291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magdalen College Choir |
E411000
|
entity |
| Predicate | performsTour |
P61809
|
FINISHED |
| Object | concert tours in the United Kingdom |
—
|
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: concert tours in the United Kingdom | Statement: [Magdalen College Choir, performsTour, concert tours in the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsTour Context triple: [Magdalen College Choir, performsTour, concert tours in the United Kingdom]
-
A.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
-
B.
tourWith
chosen
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
C.
followsTour
Indicates that one entity attends or participates in a tour that occurs after, or as a consequence of, another specified event or tour.
-
D.
previousTour
Indicates that one entity represents a tour that occurred before another tour in a sequence or timeline.
-
E.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfafc8448190a25be8ada84eff9c |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.