Triple
T6794797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eco-Power Stadium |
E156026
|
entity |
| Predicate | hasSecondarySport |
P17808
|
FINISHED |
| Object | rugby league |
—
|
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: rugby league | Statement: [Eco-Power Stadium, hasSecondarySport, rugby league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondarySport Context triple: [Eco-Power Stadium, hasSecondarySport, rugby league]
-
A.
secondarySport
chosen
Indicates that an entity participates in or is associated with a sport that is not their primary or main sport.
-
B.
primarySport
Indicates the main sport with which an entity (such as a person, team, or organization) is most closely associated or primarily involved.
-
C.
hasMajorSport
Indicates that an entity is associated with or participates in a primary or most prominent sport.
-
D.
primarySports
Indicates that a particular sport is the main or most important sport associated with an entity (such as a person, team, or organization).
-
E.
alsoUsedForSport
Indicates that something primarily associated with one purpose is additionally used for sporting activities or athletic purposes.
- 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2c59648819081736d27d52d957f |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.