Triple
T12093852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Cambridge |
E288015
|
entity |
| Predicate | holderBecame |
P103466
|
FINISHED |
| Object | Prince of Wales in 2022 |
—
|
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: Prince of Wales in 2022 | Statement: [Duke of Cambridge, holderBecame, Prince of Wales in 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderBecame Context triple: [Duke of Cambridge, holderBecame, Prince of Wales in 2022]
-
A.
holderMayBe
Indicates that a particular entity is allowed or permitted to serve as the holder or possessor of another entity.
-
B.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
C.
tenantBecame
Indicates that an entity transitioned into the role or status of a tenant at a particular time or under specific conditions.
-
D.
holder
Indicates that one entity possesses, controls, or has custody of another entity, typically in a temporary or contextual sense.
-
E.
memberBecame
Indicates that an entity transitioned into becoming a member of a group, organization, or collection at a specific point in time.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d9178814e081908f67e3846718530e |
completed | April 10, 2026, 3:30 p.m. |
Created at: April 8, 2026, 9:48 p.m.