Triple
T13781475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Slam |
E331139
|
entity |
| Predicate | GrandSlamFrequency |
P65013
|
FINISHED |
| Object | four tournaments per year |
—
|
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: four tournaments per year | Statement: [Golden Slam, GrandSlamFrequency, four tournaments per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GrandSlamFrequency Context triple: [Golden Slam, GrandSlamFrequency, four tournaments per year]
-
A.
GrandSlams
Indicates that an entity has won or is associated with victories in major Grand Slam tournaments within a given sport.
-
B.
grandSlam
Indicates achieving a particularly comprehensive or dominant success, often by winning all major components or events within a defined set.
-
C.
grandSlamOrder
Indicates that one event or achievement in a sequence is a grand slam and specifies its relative order or position among other such events.
-
D.
otherGrandSlams
Indicates that an entity is associated with Grand Slam tournaments other than a primary or specifically referenced one.
-
E.
frequencyOfTournament
chosen
Indicates how often a particular tournament takes place within a given time period.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02460a688190a27874f8d35819c7 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe98b5bc8190967907ec64d0317d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:11 p.m.