Triple
T12717584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John de Bohun, 5th Earl of Hereford |
E303888
|
entity |
| Predicate | marriageWithoutIssue |
P93865
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [John de Bohun, 5th Earl of Hereford, marriageWithoutIssue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageWithoutIssue Context triple: [John de Bohun, 5th Earl of Hereford, marriageWithoutIssue, true]
-
A.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
B.
marriageResolvedBy
Indicates that a marital relationship between two parties has been formally concluded or dissolved through a specific resolving action or process (e.g., divorce, annulment).
-
C.
marriageOutcome
chosen
Indicates the result or status that follows from a marriage, such as whether it continues, ends, or changes form.
-
D.
marries
Indicates that one entity enters into a legally or socially recognized marital union with another entity.
-
E.
hasNotableMarriage
Indicates a marital relationship involving the subject that is considered significant or noteworthy in some context.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620bd6148190a2f50067a4c18c14 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.