Triple
T19646451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen mother of the United Kingdom |
E471683
|
entity |
| Predicate | mayHoldTitleConcurrentlyWith |
P79154
|
FINISHED |
| Object | princess |
—
|
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: princess | Statement: [Queen mother of the United Kingdom, mayHoldTitleConcurrentlyWith, princess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHoldTitleConcurrentlyWith Context triple: [Queen mother of the United Kingdom, mayHoldTitleConcurrentlyWith, princess]
-
A.
mayBeHeldConcurrentlyWith
Indicates that one event, state, or condition is allowed to occur or be in effect at the same time as another without conflict or violation of constraints.
-
B.
mayHoldTitleOf
Indicates that an entity is permitted or eligible to possess or bear a particular title.
-
C.
heldConcurrentlyWith
Indicates that two or more events, roles, or states occurred or were in effect at the same time.
-
D.
titleHeldConcurrentlyWith
chosen
Indicates that one title or position was held at the same time as another title or position by the same entity.
-
E.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64125dd9481908a891c71c975a964 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.