Triple
T31303916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukedom of Cambridge |
E798281
|
entity |
| Predicate | usedByConsort |
P47492
|
FINISHED |
| Object | Catherine, Duchess of Cambridge |
—
|
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: Catherine, Duchess of Cambridge | Statement: [Dukedom of Cambridge, usedByConsort, Catherine, Duchess of Cambridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByConsort Context triple: [Dukedom of Cambridge, usedByConsort, Catherine, Duchess of Cambridge]
-
A.
usedAsConsortsIn
Indicates that the entities served in the role of consorts within a specified context, such as a reign, period, or relationship.
-
B.
providedConsortTo
chosen
Indicates that one entity served as the consort (spouse or partner) to another entity.
-
C.
usesConsortiumModel
Indicates that an entity operates under or applies a consortium-based model, typically involving shared governance, resources, or collaboration among multiple organizations.
-
D.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
E.
associatedConsort
Indicates a spousal or consort relationship linking one entity to another as their partner.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 29, 2026, 9:14 p.m.