Triple
T27769490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACC Championship 2013 |
E701700
|
entity |
| Predicate | awayTeamConferenceDivision |
P34054
|
FINISHED |
| Object | Coastal Division |
—
|
NE NERFINISHED |
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: Coastal Division | Statement: [ACC Championship 2013, awayTeamConferenceDivision, Coastal Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awayTeamConferenceDivision Context triple: [ACC Championship 2013, awayTeamConferenceDivision, Coastal Division]
-
A.
awayTeamDivision
chosen
Indicates the competitive division or grouping to which the away team belongs in a league or tournament structure.
-
B.
awayTeamConference
Indicates the athletic conference to which the away (visiting) team belongs in a sporting event.
-
C.
homeTeamDivisionOrConference
Indicates the division or conference to which the home team in a game or matchup belongs.
-
D.
opponentTeamConference
Indicates the athletic conference to which the opposing team belongs in a given competition or matchup.
-
E.
losingTeamConference
Indicates the conference or league affiliation of the team that lost a given game or match.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6379527cc8190b835dcf330096a64 |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:33 p.m.