Triple
T812365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish League Cup |
E17572
|
entity |
| Predicate | domesticCupHierarchyPosition |
P19889
|
FINISHED |
| Object | second major cup competition in Scotland |
—
|
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: second major cup competition in Scotland | Statement: [Scottish League Cup, domesticCupHierarchyPosition, second major cup competition in Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticCupHierarchyPosition Context triple: [Scottish League Cup, domesticCupHierarchyPosition, second major cup competition in Scotland]
-
A.
domesticCup
Indicates that an entity has won or participated in a domestic (national-level) cup competition within its sport or domain.
-
B.
domesticCupQualifierFor
Indicates that a team has qualified for participation in a domestic cup competition.
-
C.
nestLocation
Indicates the place or environment where an animal or organism builds or maintains its nest.
-
D.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
E.
positionOnFranchise
Indicates the specific role, rank, or status an entity holds within a particular franchise or franchise-based organization.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab4c7418819085cb64c6bf5fa70c |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa73df08819096d0553a4b2509de |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4781c88190ae36906251347cdc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.