Triple
T5624684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papa Johns Trophy |
E147690
|
entity |
| Predicate | namingRights |
P3318
|
FINISHED |
| Object | title sponsorship of EFL Trophy |
—
|
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: title sponsorship of EFL Trophy | Statement: [Papa Johns Trophy, namingRights, title sponsorship of EFL Trophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingRights Context triple: [Papa Johns Trophy, namingRights, title sponsorship of EFL Trophy]
-
A.
namingRightsBrand
Indicates that a brand holds the official naming rights for a venue, event, or property.
-
B.
namingRightsHolder
chosen
Indicates which entity holds the official right to name or brand another entity (such as a venue, event, or asset).
-
C.
namingRightsLocation
Indicates that an entity holds the naming rights specifically for a given location or venue.
-
D.
namingRightsReplaced
Indicates that one entity’s naming rights to something have been superseded or taken over by another entity’s naming rights.
-
E.
namingRightsEndYear
Indicates the calendar year in which an entity’s contractual right to have its name associated with another entity (e.g., a venue, event, or asset) expires.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022165d8c8190b2a14f1cd0a45ecc |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.