Triple
T12383189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sedbergh School |
E295792
|
entity |
| Predicate | sportsEmphasis |
P6214
|
FINISHED |
| Object | rugby union |
—
|
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: rugby union | Statement: [Sedbergh School, sportsEmphasis, rugby union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsEmphasis Context triple: [Sedbergh School, sportsEmphasis, rugby union]
-
A.
sportFocus
chosen
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
B.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
-
C.
sportsAttraction
Indicates a relationship where an entity serves as a venue, site, or draw specifically for sports-related activities or events.
-
D.
sportsAndRecreation
Indicates a relationship where an entity is associated with, involved in, or designated for sports or recreational activities.
-
E.
sportsCategory
Indicates that one entity is classified as a type or category within the domain of sports to which the other entity belongs.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fbc3f608190b0ee3c4f304a94db |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.