Triple
T28023654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organizational Unit |
E707752
|
entity |
| Predicate | canBeProtectedFrom |
P38210
|
FINISHED |
| Object | accidental deletion |
—
|
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: accidental deletion | Statement: [Organizational Unit, canBeProtectedFrom, accidental deletion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeProtectedFrom Context triple: [Organizational Unit, canBeProtectedFrom, accidental deletion]
-
A.
isProtectedFrom
chosen
Indicates that one entity is safeguarded or shielded against harm, damage, or adverse effects caused by another entity or factor.
-
B.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
C.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
hasProtectionCriterion
Indicates that something is associated with a specific condition or standard used to determine its protection requirements or status.
-
E.
isOverprotectedBy
Indicates that one entity receives an excessive or overly controlling level of protection from another entity.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 27, 2026, 8:11 p.m.