Triple
T18798249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stop the Service Charge |
E459692
|
entity |
| Predicate | seeksChangeIn |
P28300
|
FINISHED |
| Object | UK defence policy |
—
|
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: UK defence policy | Statement: [Stop the Service Charge, seeksChangeIn, UK defence policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksChangeIn Context triple: [Stop the Service Charge, seeksChangeIn, UK defence policy]
-
A.
seeksStatusChange
chosen
Indicates an entity’s intention or attempt to alter the current state, condition, or status of another entity or situation.
-
B.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
C.
changesWith
Indicates that one entity varies or is modified in response to changes in another entity.
-
D.
changesMindAfter
Indicates that one entity revises or reverses a previously held decision, opinion, or intention after another entity’s action, statement, or influence.
-
E.
soughtTo
Indicates that one entity attempted or intended to obtain, achieve, or bring about another entity or outcome.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a0215084819086bce60f95d08409 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.