Triple
T6856029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raiders |
E158145
|
entity |
| Predicate | joinedLeagueAs |
P51847
|
FINISHED |
| Object | American Football League (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: American Football League (AFL) franchise | Statement: [Raiders, joinedLeagueAs, American Football League (AFL) franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedLeagueAs Context triple: [Raiders, joinedLeagueAs, American Football League (AFL) franchise]
-
A.
joinedLeagueInSeason
Indicates that an entity became a member of a particular league starting in a specified season.
-
B.
memberOfSportsLeague
chosen
Indicates that an entity is formally part of, or participates as a member in, a specific sports league.
-
C.
rejoinedLeagueName
Indicates that an entity has returned to and become a member again of a previously left league identified by its name.
-
D.
joinedTeamInSeason
Indicates that an entity became a member of a specific team during a particular season.
-
E.
playedInLeagueThatBecame
Indicates that an entity participated in a sports league which later transformed into, merged into, or was rebranded as another specified league.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:20 p.m.