Triple
T11018576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oath of Allegiance (United Kingdom) |
E260427
|
entity |
| Predicate | consequenceOfRefusal |
P72727
|
FINISHED |
| Object | inability to take a seat in Parliament |
—
|
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: inability to take a seat in Parliament | Statement: [Oath of Allegiance (United Kingdom), consequenceOfRefusal, inability to take a seat in Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfRefusal Context triple: [Oath of Allegiance (United Kingdom), consequenceOfRefusal, inability to take a seat in Parliament]
-
A.
resultOfRejection
chosen
Indicates that something occurs as a consequence or outcome of a prior act of rejection.
-
B.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
C.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
D.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
E.
refusedMarriageProposalFrom
Indicates that one entity declined or rejected a marriage proposal made by another entity.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797a9e8788190a0f45b52bad1bfb5 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.