Triple
T21757536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birr Castle |
E537078
|
entity |
| Predicate | notGenerallyOpenToPublic |
P34060
|
FINISHED |
| Object | main residential interiors |
—
|
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: main residential interiors | Statement: [Birr Castle, notGenerallyOpenToPublic, main residential interiors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notGenerallyOpenToPublic Context triple: [Birr Castle, notGenerallyOpenToPublic, main residential interiors]
-
A.
notOpenToGeneralPublic
chosen
Indicates that access to the subject is restricted and not available to the general public.
-
B.
closedToPublic
Indicates that access to the referenced entity is restricted so that the general public is not allowed to enter or use it.
-
C.
meetsOpenToPublic
Indicates that an entity satisfies the conditions required to be considered open and accessible to the general public.
-
D.
hasPartOpenToPublic
Indicates that some portion or component of an entity is accessible for use or visitation by the general public.
-
E.
closedOffFrom
Indicates that one entity is isolated, blocked, or prevented from accessing, interacting with, or being influenced by 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8f64d881909cf10fd420153b09 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.