Triple
T2682454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCS |
E57402
|
entity |
| Predicate | notableControversySeason |
P41468
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [BCS, notableControversySeason, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableControversySeason Context triple: [BCS, notableControversySeason, 2003]
-
A.
notableSeason
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
-
B.
notableDebateMoment
Indicates a particularly significant or memorable moment that occurred during a debate, often cited or recalled as especially impactful.
-
C.
notableConflictWith
Indicates a significant, recognized conflict or dispute that exists or has existed between the related entities.
-
D.
notableInternalConflict
Indicates a significant or historically important internal conflict occurring within an entity, such as a country, organization, or group.
-
E.
notableEpisode
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9d602848190b638e417e710a555 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd891bcd481909af5340a64ff69f9 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:54 p.m.