Triple
T13093238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British rugby league system |
E310515
|
entity |
| Predicate | cupFormat |
P40472
|
FINISHED |
| Object | knockout tournaments |
—
|
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: knockout tournaments | Statement: [British rugby league system, cupFormat, knockout tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cupFormat Context triple: [British rugby league system, cupFormat, knockout tournaments]
-
A.
typeOfCup
chosen
Indicates the specific kind or category of cup that an entity is associated with or classified as.
-
B.
cupWonWith
Indicates that a particular cup or tournament victory was achieved using or in association with a specified entity (such as a team, player, or equipment).
-
C.
domesticCup
Indicates that an entity has won or participated in a domestic (national-level) cup competition within its sport or domain.
-
D.
numberOfCups
Indicates the quantity of cups associated with a given entity or context.
-
E.
servingVessel
Indicates that one entity functions as the container or vessel used to serve another entity (such as food or drink).
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.