Triple
T2454310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Division (AFL) |
E53781
|
entity |
| Predicate | hadStandings |
P11178
|
FINISHED |
| Object | AFL East standings |
—
|
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: AFL East standings | Statement: [East Division (AFL), hadStandings, AFL East standings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadStandings Context triple: [East Division (AFL), hadStandings, AFL East standings]
-
A.
hasStandings
chosen
Indicates that an entity possesses or is associated with a set of rankings, positions, or status levels within a competitive or comparative context.
-
B.
usesRegularSeasonStandingsFor
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
C.
bestLeagueFinish
Indicates the highest final position or ranking an entity has ever achieved in a particular league or competition.
-
D.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
E.
hallOfFameStatus
Indicates whether an entity has been recognized with hall of fame status, typically signifying exceptional achievement or distinction within a particular field.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:44 p.m.