Triple
T20415879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Sly |
E500710
|
entity |
| Predicate | deceivedIntoBelieving |
P7322
|
FINISHED |
| Object | he is a lord |
—
|
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: he is a lord | Statement: [Christopher Sly, deceivedIntoBelieving, he is a lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deceivedIntoBelieving Context triple: [Christopher Sly, deceivedIntoBelieving, he is a lord]
-
A.
tricked
chosen
Indicates that one entity intentionally deceived another into believing something false or acting under a false impression.
-
B.
usedMeansOfDeception
Indicates that one entity employed a particular method or tool specifically to deceive another entity.
-
C.
betrayed
Indicates that one entity has broken the trust, loyalty, or confidence of another, typically by acting against their interests or revealing something meant to be kept secret.
-
D.
typeOfDeception
Indicates the specific kind or category of deceptive act that one entity employs toward another or in a given context.
-
E.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a437eec8190a20c89a236dd5bc0 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.