Triple
T30266069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fetteresso, Kincardineshire |
E769647
|
entity |
| Predicate | hasRoyalConnections |
P917
|
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: [Fetteresso, Kincardineshire, hasRoyalConnections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalConnections Context triple: [Fetteresso, Kincardineshire, hasRoyalConnections, true]
-
A.
hasRoyalConnection
chosen
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
B.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
C.
hasRoyalFamilyMember
Indicates that one entity is a member of the royal family associated with another entity.
-
D.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
E.
hasDynasticConnections
Indicates that one entity is related to another through familial or hereditary ties between ruling or noble dynasties.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 29, 2026, 7:43 p.m.