Triple
T31425019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basement of the White House |
E801636
|
entity |
| Predicate | notGenerallyAccessibleTo |
P34060
|
FINISHED |
| Object | 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: public | Statement: [Basement of the White House, notGenerallyAccessibleTo, public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notGenerallyAccessibleTo Context triple: [Basement of the White House, notGenerallyAccessibleTo, public]
-
A.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
B.
notOpenToGeneralPublic
chosen
Indicates that access to the subject is restricted and not available to the general public.
-
C.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
D.
isDifficultToAccess
Indicates that reaching, using, or obtaining the referenced entity requires significant effort, obstacles, or special conditions.
-
E.
accessRestrictedTo
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:52 p.m.