Triple
T32663828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Walker Cup team |
E835100
|
entity |
| Predicate | competitionDates |
P96554
|
FINISHED |
| Object | September 7–8, 2019 |
—
|
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: September 7–8, 2019 | Statement: [2019 Walker Cup team, competitionDates, September 7–8, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionDates Context triple: [2019 Walker Cup team, competitionDates, September 7–8, 2019]
-
A.
skillsCompetitionDate
Indicates the date on which a skills competition takes place or is scheduled.
-
B.
bubbleTournamentDates
Indicates the scheduled dates during which a bubble-style tournament takes place.
-
C.
competitionCalendar
chosen
Indicates that there is a scheduled set of competitive events or matches associated with an entity over a defined period.
-
D.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
E.
eliteEightDateRange
Indicates the date range during which the Elite Eight round of a tournament takes place.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 1, 2026, 1:08 a.m.