Triple
T829896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Challenge Cup |
E17939
|
entity |
| Predicate | sponsorDependentName |
P15097
|
FINISHED |
| Object | title sponsorship |
—
|
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 | Statement: [Scottish Challenge Cup, sponsorDependentName, title sponsorship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorDependentName Context triple: [Scottish Challenge Cup, sponsorDependentName, title sponsorship]
-
A.
co-signer
Indicates that one entity agrees to share legal and financial responsibility for another entity’s obligation, such as a loan or contract.
-
B.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
C.
sponsorType
Indicates the specific role or category of sponsorship that an entity provides in relation to another entity or event.
-
D.
sponsorshipName
chosen
Indicates the name or title associated with a sponsorship relationship between entities.
-
E.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb384988190949d2df65662f76d |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.