Triple
T23593485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobart family |
E582546
|
entity |
| Predicate | titleCreationBy |
P46587
|
FINISHED |
| Object | James I of England |
—
|
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: James I of England | Statement: [Hobart family, titleCreationBy, James I of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCreationBy Context triple: [Hobart family, titleCreationBy, James I of England]
-
A.
titleCreation
chosen
Indicates that an entity is responsible for creating, originating, or authoring the title associated with another entity.
-
B.
titleCreatedFrom
Indicates that a title is derived or generated from another source, such as an existing entity, text, or identifier.
-
C.
titleCreationType
Indicates the manner or process by which a title was generated, assigned, or established for an entity.
-
D.
createdTitleBy
Indicates that a title (such as a work, document, or creative piece) was created by a specific agent or creator.
-
E.
associatedTitleCreation
Indicates that one entity is linked to the creation or origination of a particular title associated with 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08d63dc81908c092a87cf61f2b9 |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.