Triple
T25446576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTN8 |
E637651
|
entity |
| Predicate | cupStructure |
P8324
|
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: [MTN8, cupStructure, single-elimination ties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cupStructure Context triple: [MTN8, cupStructure, single-elimination ties]
-
A.
typeOfCup
Indicates the specific kind or category of cup that an entity is associated with or classified as.
-
B.
cupPoles
Indicates that one entity holds or supports another in a concave, cup-like manner, typically cradling or stabilizing it.
-
C.
hipStructure
Indicates a structural or anatomical relationship involving the hip, such as how its components are organized, connected, or configured.
-
D.
cupEdition
Indicates the specific edition or iteration of a recurring cup or tournament that an instance is associated with.
-
E.
cupCompetition
chosen
Indicates a competitive event or tournament, typically in a knockout or cup format, held between teams or individuals.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f70455f48190b23c09dbed884015 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:02 p.m.