Triple
T819289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Region |
E17716
|
entity |
| Predicate | includesTeamsFrom |
P12024
|
FINISHED |
| Object | multiple NCAA Division I conferences |
—
|
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: multiple NCAA Division I conferences | Statement: [West Region, includesTeamsFrom, multiple NCAA Division I conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTeamsFrom Context triple: [West Region, includesTeamsFrom, multiple NCAA Division I conferences]
-
A.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
-
B.
includesOrganization
chosen
Indicates that one entity contains, encompasses, or has within it the specified organization as a component, member, or part.
-
C.
supportsTeam
Indicates that one entity provides backing, assistance, or endorsement to a particular team.
-
D.
isTeamSpecific
Indicates that something applies only to, or is restricted to, a particular team rather than being general or shared across multiple teams.
-
E.
managedTeamFrom
Indicates that one entity led, directed, or supervised a team originating from or based in another specified entity.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab976094819086d676404d745750 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa76a7808190ac7fd9ba1a4cebcb |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.