Triple
T3106579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indianapolis Jets |
E64844
|
entity |
| Predicate | joinedBAAIn |
P45970
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Indianapolis Jets, joinedBAAIn, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedBAAIn Context triple: [Indianapolis Jets, joinedBAAIn, 1948]
-
A.
joinedABA
Indicates that an entity became a member of or entered into an organization, group, or association referred to as ABA.
-
B.
formerBAATeam
Indicates that an entity previously belonged to or was a member of a BA (Business Analyst or similarly designated) team, but is no longer part of that team.
-
C.
joinedConferenceYear
Indicates the year in which an entity became a participant or member of a particular conference.
-
D.
originalBAATeam
Indicates that an entity is (or was) a member of the original BAA team associated with another entity (such as an organization, project, or initiative).
-
E.
joinedLeagueInSeason
Indicates that an entity became a member of a particular league starting in a specified season.
- F. None of above. chosen
Provenance (4 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29d4aa8819093287bc71370fc05 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.