Triple
T12185124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadline |
E290313
|
entity |
| Predicate | causedReactionFrom |
P97670
|
FINISHED |
| Object | United States government censors |
—
|
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: United States government censors | Statement: [Deadline, causedReactionFrom, United States government censors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causedReactionFrom Context triple: [Deadline, causedReactionFrom, United States government censors]
-
A.
causedReaction
chosen
Indicates that one entity’s action or state brought about a specific reaction or response in another entity.
-
B.
relatedReaction
Indicates that one reaction is connected or associated with another reaction in some relevant way.
-
C.
receivedReaction
Indicates that an entity has been the target of a reaction or response from another entity.
-
D.
reaction
Indicates a chemical or physical process in which one set of substances or conditions transforms into another, often involving interaction, change, or response between entities.
-
E.
featuresReaction
Indicates that one entity exhibits, displays, or includes a particular reaction associated with another entity or context.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91a83012c81908d04bbab5fdcd8c2 |
completed | April 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69d91510a258819090ef8fbdc2d8707b |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.