Triple
T21653284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White U House |
E534392
|
entity |
| Predicate | privacyStrategy |
P15689
|
FINISHED |
| Object | blank exterior walls |
—
|
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: blank exterior walls | Statement: [White U House, privacyStrategy, blank exterior walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privacyStrategy Context triple: [White U House, privacyStrategy, blank exterior walls]
-
A.
privacyProperty
Indicates that one entity has a characteristic, rule, or condition specifically related to privacy in the context of the relationship.
-
B.
privacyCharacteristic
chosen
Indicates the specific privacy-related property or feature that characterizes how information is handled, protected, or exposed in a given context.
-
C.
soughtPrivacy
Indicates that an entity intentionally attempted to obtain or maintain privacy from others.
-
D.
ethicalPolicy
Indicates that an entity has, follows, or is governed by a specified ethical policy or set of moral guidelines.
-
E.
dataPolicy
Indicates that one entity defines or governs how data related to another entity is collected, used, stored, or shared.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59164fe081908abd2e33dcd67def |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.