Triple
T11505664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apology against Jerome |
E272775
|
entity |
| Predicate | stanceTowardJerome |
P99843
|
FINISHED |
| Object | hostile |
—
|
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: hostile | Statement: [Apology against Jerome, stanceTowardJerome, hostile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceTowardJerome Context triple: [Apology against Jerome, stanceTowardJerome, hostile]
-
A.
stanceTowardRome
Indicates the nature or attitude of an entity’s position or policy in relation to Rome.
-
B.
relationshipWithHumbertHumbert
Indicates that an entity has a specified type of personal, emotional, or social relationship with Humbert Humbert.
-
C.
isSympatheticTo
Indicates that one entity feels or expresses compassion, understanding, or emotional support toward another entity.
-
D.
showsAttitudeTowardChivalry
Indicates that an entity expresses or demonstrates a particular stance, feeling, or evaluation regarding chivalry.
-
E.
isNeutralAbout
Indicates that one entity has no strong positive or negative opinion, preference, or stance toward another entity or subject.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db2f4b08190801de1b773932f59 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.