Triple
T7579300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Dowager of Sweden |
E179443
|
entity |
| Predicate | mayCoexistWith |
P56284
|
FINISHED |
| Object | reigning Queen Consort of Sweden |
—
|
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: reigning Queen Consort of Sweden | Statement: [Queen Dowager of Sweden, mayCoexistWith, reigning Queen Consort of Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayCoexistWith Context triple: [Queen Dowager of Sweden, mayCoexistWith, reigning Queen Consort of Sweden]
-
A.
canCoexistWith
chosen
Indicates that two entities are able to exist together in the same context or environment without conflict, interference, or mutual exclusion.
-
B.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
C.
maySitWith
Indicates that one entity is permitted or allowed to sit together with another entity.
-
D.
mayDifferFrom
Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
-
E.
mayAlsoBeCalled
Indicates that one entity can alternatively be referred to by another name or label.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f975bbc08190aec30f902eaea494 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:52 p.m.