Triple
T9127624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Su Su Nway |
E219003
|
entity |
| Predicate | hasRisked |
P59284
|
FINISHED |
| Object | personal freedom for activism |
—
|
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: personal freedom for activism | Statement: [Su Su Nway, hasRisked, personal freedom for activism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRisked Context triple: [Su Su Nway, hasRisked, personal freedom for activism]
-
A.
riskTaken
chosen
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
-
B.
hasCountryOfRisk
Indicates that an entity is associated with a country where it faces significant exposure, vulnerability, or potential risk.
-
C.
hasWithdrawalRisk
Indicates that discontinuing or reducing something is associated with a risk of withdrawal effects or adverse reactions.
-
D.
riskIfBreached
Indicates that a breach of the referenced entity or condition would expose or create a potential risk or harm.
-
E.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8cad9c0819082d61f53865ef0b4 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.