Triple
T34319814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Honourable Augusta Emma Wilde |
E880701
|
entity |
| Predicate | hasIllegitimateRoyalAncestry |
P178881
|
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: [The Honourable Augusta Emma Wilde, hasIllegitimateRoyalAncestry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIllegitimateRoyalAncestry Context triple: [The Honourable Augusta Emma Wilde, hasIllegitimateRoyalAncestry, true]
-
A.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
B.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
C.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
-
D.
hasNoRoyalTitle
Indicates that an entity does not possess any royal title or rank.
-
E.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
- F. None of above. chosen
Provenance (4 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71782422c81908196d5e4a610cb1a |
completed | May 3, 2026, 9:38 a.m. |
Created at: May 1, 2026, 1:57 a.m.