Triple
T12627682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Honourable Lady Ogilvy |
E301557
|
entity |
| Predicate | holderPerforms |
P68218
|
FINISHED |
| Object | royal engagements |
—
|
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: royal engagements | Statement: [The Honourable Lady Ogilvy, holderPerforms, royal engagements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderPerforms Context triple: [The Honourable Lady Ogilvy, holderPerforms, royal engagements]
-
A.
holderConducts
chosen
Indicates that the holder actively organizes, carries out, or performs the specified event, activity, or process.
-
B.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
C.
performsAs
Indicates that one entity takes on, enacts, or fulfills the role, function, or character of another entity.
-
D.
holderMustBe
Indicates that a specified entity is required to be the holder or possessor of another entity or resource.
-
E.
holderMayBe
Indicates that a particular entity is allowed or permitted to serve as the holder or possessor of 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:14 p.m.