Triple
T26590731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craufurd baronets |
E667345
|
entity |
| Predicate | hasNobleFamilyName |
P186972
|
FINISHED |
| Object | Craufurd |
—
|
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: Craufurd | Statement: [Craufurd baronets, hasNobleFamilyName, Craufurd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobleFamilyName Context triple: [Craufurd baronets, hasNobleFamilyName, Craufurd]
-
A.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
B.
hasNobleHouseOrigin
Indicates that an entity originates from, or is ancestrally associated with, a particular noble house.
-
C.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
D.
hasAncestralFamilyName
chosen
Indicates that an entity bears or is associated with a family name inherited from its ancestors.
-
E.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 27, 2026, 2:07 a.m.