Triple
T26831269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CURUFC |
E675505
|
entity |
| Predicate | playsAnnualMatchAt |
P167304
|
FINISHED |
| Object | Twickenham Stadium |
—
|
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: Twickenham Stadium | Statement: [CURUFC, playsAnnualMatchAt, Twickenham Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsAnnualMatchAt Context triple: [CURUFC, playsAnnualMatchAt, Twickenham Stadium]
-
A.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
B.
playedSeasonType
Indicates that an entity participated in or was involved with a particular type of season (e.g., regular season, playoffs, preseason) within a competition or schedule.
-
C.
playsTwicePerSeason
Indicates that one entity participates in or performs the specified activity or event exactly two times during each season.
-
D.
matchdayActivity
Indicates the specific activity, event, or engagement that takes place in connection with a particular match day.
-
E.
seasonParticipatedIn
Indicates that an entity took part in or was active during a specific season of a recurring event, series, or competition.
- F. None of above. chosen
Provenance (4 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 27, 2026, 5:01 a.m.