Triple
T5475185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference USA women's basketball competition |
E122934
|
entity |
| Predicate | teamClassification |
P2705
|
FINISHED |
| Object | varsity |
—
|
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: varsity | Statement: [Conference USA women's basketball competition, teamClassification, varsity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamClassification Context triple: [Conference USA women's basketball competition, teamClassification, varsity]
-
A.
typeOfTeams
chosen
Indicates the categories or kinds of teams to which an entity or group of entities belongs.
-
B.
teamDivision
Indicates how a larger team is split into smaller subgroups or units for organization or collaboration.
-
C.
goalOfClassificationBy
Indicates that an entity serves as the intended goal or objective of a particular act of classification performed by another agent or process.
-
D.
teamCodeType
Indicates the classification or category type associated with a particular team code.
-
E.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd923465c88190ad9c1b75b268f7ca |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.