Triple
T1776051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Three Conference |
E38980
|
entity |
| Predicate | alsoContestedSports |
P32285
|
FINISHED |
| Object | 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: basketball | Statement: [Middle Three Conference, alsoContestedSports, basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoContestedSports Context triple: [Middle Three Conference, alsoContestedSports, basketball]
-
A.
alsoContestedIn
Indicates that the same issue, claim, or matter is being disputed or challenged in another context, case, or proceeding as well.
-
B.
sportsCount
Indicates the number of sports associated with or involved in a given entity or context.
-
C.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
-
D.
competitionSurface
Indicates the type of surface or medium on which a competition or contest takes place.
-
E.
sportingAssociation
Indicates a formal relationship in which an organization serves as a governing, organizing, or affiliating body for sports activities, teams, or events.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab74db3dbc8190ab256a4e158062b8 |
completed | March 7, 2026, 12:44 a.m. |
Created at: March 4, 2026, 7:31 p.m.