Triple
T13627386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sue Bayliss |
E325619
|
entity |
| Predicate | expressesView |
P4750
|
FINISHED |
| Object | prefers financial security over idealism |
—
|
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: prefers financial security over idealism | Statement: [Sue Bayliss, expressesView, prefers financial security over idealism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expressesView Context triple: [Sue Bayliss, expressesView, prefers financial security over idealism]
-
A.
expressesViewOn
Indicates that one entity communicates or holds an opinion, stance, or perspective regarding another entity or topic.
-
B.
expresses
chosen
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
-
C.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
D.
viewsAs
Indicates that one entity perceives, interprets, or regards another entity in a particular way or role.
-
E.
expressedThrough
Indicates that something (such as an idea, emotion, or content) is conveyed, manifested, or communicated by means of a particular medium, form, or channel.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.