Triple
T25986751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zero |
E646222
|
entity |
| Predicate | riskIfSuitDamaged |
P159637
|
FINISHED |
| Object | mental harm to nearby beings |
—
|
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: mental harm to nearby beings | Statement: [Zero, riskIfSuitDamaged, mental harm to nearby beings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskIfSuitDamaged Context triple: [Zero, riskIfSuitDamaged, mental harm to nearby beings]
-
A.
damagedIn
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
-
B.
hasTypeOfDamage
Indicates that an entity experiences or exhibits a specific kind or category of damage.
-
C.
shippingRisk
Indicates the level or likelihood of potential loss, damage, or delay associated with transporting goods from one location to another.
-
D.
rimCondition
Indicates a condition or state that applies specifically to the rim or edge of an object or structure.
-
E.
lessSuitableFor
Indicates that one entity is comparatively less appropriate, effective, or fitting than another for a given purpose, context, or condition.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605446ca48190907baef523f13ccf |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:55 a.m.