Triple
T6366058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriots |
E143232
|
entity |
| Predicate | representInSport |
P17899
|
FINISHED |
| Object | men's basketball |
—
|
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: men's basketball | Statement: [Patriots, representInSport, men's basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representInSport Context triple: [Patriots, representInSport, men's basketball]
-
A.
representsInSport
chosen
Indicates that one entity serves as an official representative of another entity within the context of a particular sport or sporting domain.
-
B.
representsSportLevel
Indicates that an entity participates in or is associated with a particular level or tier within a sport.
-
C.
sponsorSport
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
-
D.
portraysSport
Indicates that one entity visually or narratively represents or depicts a particular sport.
-
E.
representsInLeague
Indicates that an entity serves as a representative of another entity within a specific league or organized competition.
- 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068106e18819087ed2e9841d2b365 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.