Triple
T11559169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Bell |
E274090
|
entity |
| Predicate | attendanceScandal |
P29490
|
FINISHED |
| Object | 1974 attendance inflation controversy |
—
|
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: 1974 attendance inflation controversy | Statement: [Philadelphia Bell, attendanceScandal, 1974 attendance inflation controversy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendanceScandal Context triple: [Philadelphia Bell, attendanceScandal, 1974 attendance inflation controversy]
-
A.
associatedScandal
chosen
Indicates a relationship where an entity is linked to, involved in, or notably connected with a particular scandal.
-
B.
timeOfMajorScandal
Indicates the specific time period during which a major scandal involving the entity occurred.
-
C.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
D.
fanIncidents
Indicates incidents or problematic events involving fans in relation to a particular subject, such as a team, event, or performance.
-
E.
attendanceAnnounced
Indicates that an official statement has been made about whether and/or how many people will attend an event.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a899d4481909a3bce3147763b51 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.