Triple
T22302045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Stadium |
E551280
|
entity |
| Predicate | regularHostOf |
P13575
|
FINISHED |
| Object | major domestic rugby matches |
—
|
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: major domestic rugby matches | Statement: [Toyota Stadium, regularHostOf, major domestic rugby matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularHostOf Context triple: [Toyota Stadium, regularHostOf, major domestic rugby matches]
-
A.
regularF1HostFrom
Indicates that an entity regularly serves as the host location for Formula 1 events originating from a specified place or jurisdiction.
-
B.
naturalHost
Indicates that one entity is the typical or primary host in which another entity (such as a parasite or pathogen) naturally lives, grows, or reproduces.
-
C.
usesHost
Indicates that one entity makes use of another entity as its host or hosting environment in order to function, operate, or reside.
-
D.
guestHosted
Indicates that one entity temporarily hosted or presented an event, show, or program in place of or alongside the usual host.
-
E.
alsoHosted
chosen
Indicates that the subject entity, in addition to others, served as a host for the same event or activity.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157245ee481909a7a3397de3ae355 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.