Triple
T11171431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Dane |
E264281
|
entity |
| Predicate | isEmbittered |
P98241
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Alexander Dane, isEmbittered, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEmbittered Context triple: [Alexander Dane, isEmbittered, true]
-
A.
harborsResentmentToward
Indicates that one entity holds ongoing bitterness, anger, or ill will directed at another entity.
-
B.
belligerentAgainst
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
-
C.
correctsAberration
Indicates that one entity counteracts, fixes, or compensates for an error, flaw, or deviation present in another entity.
-
D.
belligerentInterest
Indicates that an entity has a hostile, aggressive, or conflict-seeking attitude or stake toward another entity or situation.
-
E.
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.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e89660208190b1d9e91529f5d246 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.