Triple
T31613980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buccaneers |
E806704
|
entity |
| Predicate | rejoinedConference |
P2576
|
FINISHED |
| Object | Southern Conference |
—
|
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: Southern Conference | Statement: [Buccaneers, rejoinedConference, Southern Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejoinedConference Context triple: [Buccaneers, rejoinedConference, Southern Conference]
-
A.
adoptedAtSameConferenceAs
Indicates that two entities were adopted during the same conference event or session.
-
B.
associatedWithConference
chosen
Indicates that an entity has a connection or involvement with a specific conference, such as participation, organization, or affiliation.
-
C.
joinedConferenceYear
Indicates the year in which an entity became a participant or member of a particular conference.
-
D.
mayRejoin
Indicates that an entity is permitted or eligible to re-enter or rejoin a group, organization, or prior affiliation after having left or been removed.
-
E.
reunionWith
Indicates that two or more entities come back together after a period of separation or absence.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8a8e2e48190bfb58408029dd46a |
completed | May 3, 2026, 1:45 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:38 p.m.