Triple
T11065812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Trial of Sir Henry Vane, Kt. |
E261618
|
entity |
| Predicate | documentsOutcome |
P66636
|
FINISHED |
| Object | condemnation of Henry Vane the Younger |
—
|
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: condemnation of Henry Vane the Younger | Statement: [The Trial of Sir Henry Vane, Kt., documentsOutcome, condemnation of Henry Vane the Younger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentsOutcome Context triple: [The Trial of Sir Henry Vane, Kt., documentsOutcome, condemnation of Henry Vane the Younger]
-
A.
outcomeDocument
chosen
Indicates that a particular document serves as the result, product, or formal output generated from a process, event, or action.
-
B.
documentsNow
Indicates that an entity is currently documenting, recording, or writing about another entity at the present time.
-
C.
documentsActivity
Indicates that one entity records, describes, or provides evidence of an activity performed by another entity.
-
D.
documentList
Indicates a relationship where one entity serves as a list or collection of documents associated with another entity.
-
E.
documentTypeProduced
Indicates that one entity produces, generates, or creates a document of a specified type.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7991f84488190a974d1744a62798d |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.