Triple
T4032708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XFL |
E83751
|
entity |
| Predicate | relationshipToNFL |
P53560
|
FINISHED |
| Object | not officially affiliated with the NFL |
—
|
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: not officially affiliated with the NFL | Statement: [XFL, relationshipToNFL, not officially affiliated with the NFL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToNFL Context triple: [XFL, relationshipToNFL, not officially affiliated with the NFL]
-
A.
relationshipToMLB
Indicates the nature or type of connection an entity has to Major League Baseball (MLB), such as affiliation, role, or involvement.
-
B.
hasBrotherCoachingInNFL
Indicates that one person has a brother who is serving as a coach in the National Football League (NFL).
-
C.
joinedNFL
Indicates that an entity became a member of, or started playing in, the National Football League (NFL).
-
D.
ownerDuringNFLEra
Indicates that a person or entity held ownership of an NFL team during a specified NFL era or time period.
-
E.
roleAtTampaBayBuccaneers
Indicates that an entity holds or held a specific role or position within the Tampa Bay Buccaneers organization.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb0f776881909db6b7df1db7664c |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:36 p.m.