Triple
T598859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balmoral Castle |
E11447
|
entity |
| Predicate | notOpenWhen |
P12551
|
FINISHED |
| Object | royal family in residence |
—
|
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 family in residence | Statement: [Balmoral Castle, notOpenWhen, royal family in residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notOpenWhen Context triple: [Balmoral Castle, notOpenWhen, royal family in residence]
-
A.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
-
B.
openStatus
Indicates whether an entity (such as a place, service, or resource) is currently open or available for use.
-
C.
closedDuring
chosen
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
D.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49dc4f7d08190990f70b9b3af6ce5 |
completed | March 1, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69a49cf59cd0819084e67981cb371e25 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.