Triple
T19030743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Captive |
E465727
|
entity |
| Predicate | timePeriodOfCensorship |
P133631
|
FINISHED |
| Object | late 1920s |
—
|
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 1920s | Statement: [The Captive, timePeriodOfCensorship, late 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfCensorship Context triple: [The Captive, timePeriodOfCensorship, late 1920s]
-
A.
censorshipStatusAtTime
Indicates the censorship status of something at a specific point in time, capturing whether and how it was censored then.
-
B.
censorshipYear
Indicates the year in which an act of censorship was imposed on the referenced content or entity.
-
C.
censorshipEvent
Indicates an event in which information, expression, or communication is suppressed, restricted, or altered by some controlling authority or mechanism.
-
D.
censorshipLevel
Indicates the degree or strictness of control, suppression, or restriction applied to information, media, or expression.
-
E.
censorshipAbolishedBy
Indicates that an act or policy of censorship is ended, removed, or nullified through the action or decision of a specified agent or authority.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d7404d748190bcb51692fb822fd4 |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8f6f7c8190af645bf08823ee2b |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.