Triple
T33701416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Birling |
E863463
|
entity |
| Predicate | changeOverPlay |
P179363
|
FINISHED |
| Object | shows little genuine remorse |
—
|
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: shows little genuine remorse | Statement: [Arthur Birling, changeOverPlay, shows little genuine remorse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeOverPlay Context triple: [Arthur Birling, changeOverPlay, shows little genuine remorse]
-
A.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
B.
changeoverRule
Indicates the rule or conditions that govern when and how a change from one state, configuration, or period to another should occur.
-
C.
changesWith
Indicates that one entity varies or is modified in response to changes in another entity.
-
D.
changesProperty
Indicates that one entity causes a change in a specific property or attribute of another entity.
-
E.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 1:43 a.m.