Triple
T11299855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Firemen’s Ball |
E267553
|
entity |
| Predicate | yearOfCensorship |
P33844
|
FINISHED |
| Object | late 1960s |
—
|
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: late 1960s | Statement: [The Firemen’s Ball, yearOfCensorship, late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfCensorship Context triple: [The Firemen’s Ball, yearOfCensorship, late 1960s]
-
A.
censorshipYear
chosen
Indicates the year in which an act of censorship was imposed on the referenced content or entity.
-
B.
censorshipStatusAtTime
Indicates the censorship status of something at a specific point in time, capturing whether and how it was censored then.
-
C.
suppressionYear
Indicates the year in which the referenced activity, expression, or entity was formally suppressed, halted, or forcibly discontinued.
-
D.
wasCensored
Indicates that an entity’s content, expression, or communication was suppressed, altered, or restricted by an authority or controlling party.
-
E.
censorshipReason
Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a4aad4819097384e1b591be2e3 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.