Triple
T31701604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1930 NFL season |
E809069
|
entity |
| Predicate | teamJoinedLeague |
P166872
|
FINISHED |
| Object | Portsmouth Spartans |
—
|
NE NERFINISHED |
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: Portsmouth Spartans | Statement: [1930 NFL season, teamJoinedLeague, Portsmouth Spartans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamJoinedLeague Context triple: [1930 NFL season, teamJoinedLeague, Portsmouth Spartans]
-
A.
joinedLeagueInSeason
Indicates that an entity became a member of a particular league starting in a specified season.
-
B.
enteredLeagueAs
chosen
Indicates that an entity joined or was admitted into a particular league, typically marking the start of its participation in that league.
-
C.
joinedLeagueAsExpansionTeamWith
Indicates that an entity entered a league as a newly created expansion team together with another specified entity.
-
D.
rejoinedLeagueName
Indicates that an entity has returned to and become a member again of a previously left league identified by its name.
-
E.
managedTeamLeague
Indicates that a person or organization had managerial responsibility for a team participating in a particular 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:12 p.m.