Triple
T13340638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Stanley |
E317813
|
entity |
| Predicate | helpedTo |
P33868
|
FINISHED |
| Object | secure Henry Tudor’s victory at Bosworth Field |
—
|
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: secure Henry Tudor’s victory at Bosworth Field | Statement: [William Stanley, helpedTo, secure Henry Tudor’s victory at Bosworth Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedTo Context triple: [William Stanley, helpedTo, secure Henry Tudor’s victory at Bosworth Field]
-
A.
helpedCause
chosen
Indicates that one entity contributed to bringing about, enabling, or facilitating an outcome or event involving another entity.
-
B.
oftenHelps
Indicates that one entity frequently provides assistance or support to another.
-
C.
crossedWithHelpOf
Indicates that one entity moved across or through something with assistance provided by another entity or means.
-
D.
especiallyHelpsWhen
Indicates that one entity is particularly beneficial or effective in assisting another entity or situation under certain conditions or circumstances.
-
E.
wasAssistedBy
Indicates that an entity carried out an action or achieved a result with the help or support of 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99d0379d481909a50fff31b19fed1 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.