Triple
T25696768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Junior Cup |
E644341
|
entity |
| Predicate | matchOutcomeRule |
P159485
|
FINISHED |
| Object | single-elimination ties |
—
|
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: single-elimination ties | Statement: [Scottish Junior Cup, matchOutcomeRule, single-elimination ties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchOutcomeRule Context triple: [Scottish Junior Cup, matchOutcomeRule, single-elimination ties]
-
A.
commonMatchOutcomeTypes
Indicates that the related entities share the same typical or frequently occurring types of outcomes for a match or contest.
-
B.
matchResult
Indicates the outcome or final status produced by a particular match or game between participants.
-
C.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
D.
matchResultInfluenced
Indicates that the outcome of a match was affected or altered by a specified factor, event, or condition.
-
E.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fbc4f1e88190bd5b195d92e44d3e |
completed | May 2, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 8:37 p.m.