Triple
T7944727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian football pyramid |
E184470
|
entity |
| Predicate | usesSeasonFormat |
P54920
|
FINISHED |
| Object | home-and-away league seasons |
—
|
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: home-and-away league seasons | Statement: [Australian football pyramid, usesSeasonFormat, home-and-away league seasons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSeasonFormat Context triple: [Australian football pyramid, usesSeasonFormat, home-and-away league seasons]
-
A.
competesInSeasonalFormat
chosen
Indicates that an entity participates in a competition that is organized into recurring seasons or seasonal formats.
-
B.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
C.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
D.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
E.
dstSeason
Indicates the specific season during which daylight saving time (DST) is in effect for a given context or location.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b285d3881909b2ac0b395538a8a |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.