Triple
T30565406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grafton family |
E777958
|
entity |
| Predicate | originOfTitleName |
P117121
|
FINISHED |
| Object | Grafton Regis, Northamptonshire |
—
|
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: Grafton Regis, Northamptonshire | Statement: [Grafton family, originOfTitleName, Grafton Regis, Northamptonshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfTitleName Context triple: [Grafton family, originOfTitleName, Grafton Regis, Northamptonshire]
-
A.
notableTitleOrigin
Indicates that a notable or distinguished title held by an entity originates from, or is derived from, a specified source or context.
-
B.
originallyTitleOf
Indicates that one title is the original title from which another work, edition, or localized title is derived.
-
C.
hasPoemTitleOrigin
Indicates that something derives its name or title from a specific poem.
-
D.
hasTitleEtymology
Indicates that the origin or derivation of a title is based on, or explained by, another term, name, or linguistic source.
-
E.
sourceOfTitle
chosen
Indicates that one entity is the origin or provider of another entity’s title or designation.
- 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: April 29, 2026, 8:21 p.m.