Triple
T26823879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Firebirds |
E675323
|
entity |
| Predicate | activeInAFLFrom |
P27086
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Indiana Firebirds, activeInAFLFrom, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInAFLFrom Context triple: [Indiana Firebirds, activeInAFLFrom, 2001]
-
A.
AFLClubDebut
Indicates the event or relationship in which a player makes their first official appearance for an AFL club.
-
B.
activeInLeague
Indicates that an entity (such as a team or player) is currently participating in or belongs to a particular league.
-
C.
AFLRepresentative
Indicates that an entity serves as an official representative or delegate within the context of the AFL (e.g., the Australian Football League or a similarly named organization).
-
D.
AFLMembershipStartYear
chosen
Indicates the year in which an entity first became a member of the AFL.
-
E.
AFLRisingStarEquivalent
Indicates that one entity is the counterpart or equivalent of another entity in terms of an AFL Rising Star–type recognition or award.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 4:57 a.m.