Triple
T5926351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Lodge, Windsor |
E131819
|
entity |
| Predicate | isNotOpenTo |
P34060
|
FINISHED |
| Object | general public |
—
|
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: general public | Statement: [Royal Lodge, Windsor, isNotOpenTo, general public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotOpenTo Context triple: [Royal Lodge, Windsor, isNotOpenTo, general public]
-
A.
notOpenToGeneralPublic
chosen
Indicates that access to the subject is restricted and not available to the general public.
-
B.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
C.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
-
D.
initiallyOpenTo
Indicates that something starts out in an open state or condition at the beginning of a process, period, or interaction.
-
E.
notClosedUnder
Indicates that applying the operation or relation to elements of a set can produce results that do not belong to that set, so the set is not closed under that operation or relation.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c033541d108190a34d1fde2fe9dacb |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.