Triple
T26963138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Dowager |
E679098
|
entity |
| Predicate | mayResideAt |
P23320
|
FINISHED |
| Object | royal court |
—
|
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 court | Statement: [Queen Dowager, mayResideAt, royal court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayResideAt Context triple: [Queen Dowager, mayResideAt, royal court]
-
A.
canResideIn
chosen
Indicates that an entity is capable of living, staying, or being located within a specified place or environment.
-
B.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
C.
hostResidenceOf
Indicates that a location serves as the primary place of residence for a specified person or group.
-
D.
hasResidenceOn
Indicates that one entity’s place of residence is located on or along another entity, such as a street, road, or other linear feature.
-
E.
residesOver
Indicates that one entity lives or is situated in a position physically higher than or above 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620ede4f88190a98f91af97505663 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:33 a.m.