Triple
T3850797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Kingdom general election, 1970 |
E85289
|
entity |
| Predicate | wasUnexpected |
P51930
|
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: [United Kingdom general election, 1970, wasUnexpected, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUnexpected Context triple: [United Kingdom general election, 1970, wasUnexpected, true]
-
A.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
B.
isSupposedToBe
Indicates that something is expected or intended to have a particular state, quality, or role, whether or not it actually does.
-
C.
encountered
Indicates that one entity came across or met another entity, typically in a specific place or context, often unexpectedly or during the course of some activity.
-
D.
anticipates
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
-
E.
triedToAvoid
Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcf67788190975105131baabc4b |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:19 p.m.