Triple
T34958140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ocampa |
E1008173
|
entity |
| Predicate | receivesFromProtector |
P185256
|
FINISHED |
| Object | energy for survival |
—
|
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: energy for survival | Statement: [Ocampa, receivesFromProtector, energy for survival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesFromProtector Context triple: [Ocampa, receivesFromProtector, energy for survival]
-
A.
isProtectedFrom
Indicates that one entity is safeguarded or shielded against harm, damage, or adverse effects caused by another entity or factor.
-
B.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
C.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
D.
receivedDecryptsFrom
Indicates that one entity has obtained or been sent decrypted information or messages from another entity.
-
E.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: May 3, 2026, 4 p.m.