Triple
T7591346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Soul |
E179741
|
entity |
| Predicate | divisionChampionship |
P78028
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Philadelphia Soul, divisionChampionship, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionChampionship Context triple: [Philadelphia Soul, divisionChampionship, 2004]
-
A.
divisionIChampionship
Indicates that an entity has won or holds a Division I championship title in a given sport or competition.
-
B.
divisionIIIChampionship
Indicates that an entity has won or is associated with a Division III-level championship in a given sport or competition.
-
C.
divisionIIChampionship
Indicates that an entity has won or holds a Division II championship title in a given sport or competition.
-
D.
divisionChampionWestern
Indicates that an entity is the champion of a division within the Western conference or region in a competitive context.
-
E.
divisionPlayedIn
Indicates that an entity (such as a team or player) participated in or was a member of a particular competitive division.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9b746ac8190b255afdfb9635f72 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:53 p.m.