Triple
T35300887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1895 Cup |
E1019500
|
entity |
| Predicate | finalUsuallyPlayedOnSameDayAs |
P15660
|
FINISHED |
| Object | Challenge Cup final |
—
|
NE NERFINISHED |
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: Challenge Cup final | Statement: [1895 Cup, finalUsuallyPlayedOnSameDayAs, Challenge Cup final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalUsuallyPlayedOnSameDayAs Context triple: [1895 Cup, finalUsuallyPlayedOnSameDayAs, Challenge Cup final]
-
A.
finalUsuallyPlayedOn
Indicates that a final (e.g., match, round, or event) is most commonly held or performed on a particular day, date, or occasion.
-
B.
finalUsuallyPlayedIn
Indicates that an event or competition’s final round is typically held in a particular location or venue.
-
C.
heldOnSameDayAs
chosen
Indicates that two events or occurrences took place on the same calendar day.
-
D.
laterPlayedWith
Indicates that one entity engaged in play with another entity at a later time than some referenced or implied earlier event.
-
E.
isOftenPlayedFor
Indicates that one entity is frequently performed, used, or presented for the benefit, enjoyment, or experience of another entity.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:03 p.m.