Triple
T23664621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurent |
E584541
|
entity |
| Predicate | attemptsToBetray |
P25014
|
FINISHED |
| Object | the Cullens |
—
|
NE NERFINISHED |
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: the Cullens | Statement: [Laurent, attemptsToBetray, the Cullens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptsToBetray Context triple: [Laurent, attemptsToBetray, the Cullens]
-
A.
betrayalType
Indicates the specific kind or category of betrayal that characterizes the relationship or action between the involved entities.
-
B.
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.
-
C.
causeOfBetrayal
Indicates that one entity is the reason or motivating factor behind another entity’s act of betrayal.
-
D.
betrayalSign
chosen
Indicates an action or signal through which one party violates the trust, loyalty, or expectations of another.
-
E.
attemptedCountercoup
Indicates an effort by a group or individual to overthrow or reverse a previous coup, aiming to restore the prior regime or alter the post-coup power structure.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40ad45c8190a3a0ae7c7f9bf3a5 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.