Triple
T33745552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Security Prison 21 |
E864687
|
entity |
| Predicate | aftermathUse |
P152085
|
FINISHED |
| Object | memorial site |
—
|
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: memorial site | Statement: [Security Prison 21, aftermathUse, memorial site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aftermathUse Context triple: [Security Prison 21, aftermathUse, memorial site]
-
A.
aftermathOf
Indicates that one event, state, or condition occurs as a consequence or result following another event.
-
B.
aftermathDescription
Indicates the description or characterization of events, conditions, or consequences that occur following a particular incident or action.
-
C.
aftermathActivity
chosen
Indicates the activity or state that occurs as a direct consequence of, or in response to, a preceding event or situation.
-
D.
aftermathDepictedIn
Indicates that the aftermath or consequences of an event or situation are depicted or represented in a given medium or work.
-
E.
aftermathPolicy
Indicates the policy, rules, or procedures that apply in the aftermath or consequences of a particular event or action.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:44 a.m.