Triple
T885660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa Bay Buccaneers |
E19123
|
entity |
| Predicate | movedToConference |
P2576
|
FINISHED |
| Object | NFC Central in 1977 |
—
|
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: NFC Central in 1977 | Statement: [Tampa Bay Buccaneers, movedToConference, NFC Central in 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedToConference Context triple: [Tampa Bay Buccaneers, movedToConference, NFC Central in 1977]
-
A.
movedToNetwork
Indicates that an entity has been transferred or relocated from its previous context into a specific network.
-
B.
associatedWithConference
chosen
Indicates that an entity has a connection or involvement with a specific conference, such as participation, organization, or affiliation.
-
C.
meetingNumber
Indicates the specific numerical identifier assigned to distinguish one meeting from others.
-
D.
movedToLeague
Indicates that an entity changed affiliation or membership from one league to another.
-
E.
functionTransferredTo
Indicates that a specific function, role, or responsibility has been moved from one entity to another.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ae787bf081909533082ca013624a |
completed | March 1, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8ff8c48190a33b00acf65c1276 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.