Triple
T32389037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Vane |
E827615
|
entity |
| Predicate | refusedPardonFrom |
P438
|
FINISHED |
| Object | British Crown |
—
|
NE NERFINISHED |
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: British Crown | Statement: [Charles Vane, refusedPardonFrom, British Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusedPardonFrom Context triple: [Charles Vane, refusedPardonFrom, British Crown]
-
A.
refusedToSurrender
Indicates that an entity deliberately chose not to give up control, possession, or submission when requested or demanded by another entity.
-
B.
soughtPardonFor
Indicates that one entity requested or attempted to obtain a formal pardon or forgiveness for another entity or for a specific action.
-
C.
rejectedBy
chosen
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
D.
refusedToAbdicate
Indicates that a person who holds power or authority declined to give up or renounce their position when expected or requested to do so.
-
E.
refusedToExplain
Indicates that an entity declined or failed to provide an explanation about something to another entity or audience.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1d3dea88190985d0faef0c85551 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:52 a.m.