Triple
T34993181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl Nelson |
E1009448
|
entity |
| Predicate | titleInheritsFrom |
P23689
|
FINISHED |
| Object | Viscount Nelson |
—
|
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: Viscount Nelson | Statement: [Earl Nelson, titleInheritsFrom, Viscount Nelson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInheritsFrom Context triple: [Earl Nelson, titleInheritsFrom, Viscount Nelson]
-
A.
typeOfTitleInheritance
Indicates the manner or rule by which a title is passed from one holder to another (e.g., hereditary, elective, or appointed succession).
-
B.
inheritsTitle
chosen
Indicates that one entity receives and assumes a formal title or rank previously held by another entity, typically through succession or inheritance.
-
C.
titleDerivedFrom
Indicates that the title of one entity is obtained or adapted from another entity.
-
D.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
-
E.
titleBasedIn
Indicates that a creative work’s title is derived from, inspired by, or directly taken from a particular source or 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 3, 2026, 4:01 p.m.