Triple
T29185750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbie |
E739863
|
entity |
| Predicate | reasonForLying |
P183114
|
FINISHED |
| Object | to avoid harming humans emotionally |
—
|
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: to avoid harming humans emotionally | Statement: [Herbie, reasonForLying, to avoid harming humans emotionally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForLying Context triple: [Herbie, reasonForLying, to avoid harming humans emotionally]
-
A.
liesUpon
Indicates that one entity is positioned resting directly on the surface of another entity.
-
B.
reasonForFakedDeath
Indicates the motive or justification behind an entity’s decision to fake or stage their own death.
-
C.
usedMeansOfDeception
Indicates that one entity employed a particular method or tool specifically to deceive another entity.
-
D.
reasonForConviction
Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
-
E.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: April 28, 2026, 11:59 a.m.