Triple
T2284701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFL All-Star |
E51360
|
entity |
| Predicate | teamAffiliationRequired |
P18786
|
FINISHED |
| Object | AFL franchise |
—
|
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 franchise | Statement: [AFL All-Star, teamAffiliationRequired, AFL franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamAffiliationRequired Context triple: [AFL All-Star, teamAffiliationRequired, AFL franchise]
-
A.
teamAffiliationStructure
Indicates the organizational relationship that defines how a team is structured, including its internal roles, hierarchy, and affiliations.
-
B.
teamEligibility
chosen
Indicates whether an entity meets the required conditions to participate as a member of a particular team.
-
C.
leagueAffiliationManaged
Indicates that one entity manages, oversees, or administers the league affiliation of another entity.
-
D.
affiliateLeague
Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
-
E.
leagueAffiliationOfTenant
Indicates the sports league with which a tenant (such as a team or club) is formally affiliated.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc245dd208190b13c5f5d05aa6990 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.