Triple
T5232670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tari Piring |
E118146
|
entity |
| Predicate | riskElement |
P62537
|
FINISHED |
| Object | dancing on broken plates |
—
|
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: dancing on broken plates | Statement: [Tari Piring, riskElement, dancing on broken plates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskElement Context triple: [Tari Piring, riskElement, dancing on broken plates]
-
A.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
B.
riskFeature
Indicates that one entity possesses or exhibits a characteristic, condition, or attribute that increases the likelihood or severity of a negative outcome for another entity or situation.
-
C.
risk
Indicates that one entity is exposed or subject to potential harm, loss, or adverse outcome arising from another entity, action, or situation.
-
D.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
-
E.
riskBasis
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b0389048190b55b7c44fe657044 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77bf1ef08190bb3487b3f3ee088c |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7aff0244819085c4799793ed0185 |
completed | March 20, 2026, 4:51 p.m. |
Created at: March 20, 2026, 1:49 p.m.