Triple
T34127403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torres Maldonado residence |
E875324
|
entity |
| Predicate | hasPrivacy |
P34695
|
FINISHED |
| Object | private dwelling |
—
|
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: private dwelling | Statement: [Torres Maldonado residence, hasPrivacy, private dwelling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrivacy Context triple: [Torres Maldonado residence, hasPrivacy, private dwelling]
-
A.
privacyProperty
Indicates that one entity has a characteristic, rule, or condition specifically related to privacy in the context of the relationship.
-
B.
soughtPrivacy
Indicates that an entity intentionally attempted to obtain or maintain privacy from others.
-
C.
privacyCharacteristic
Indicates the specific privacy-related property or feature that characterizes how information is handled, protected, or exposed in a given context.
-
D.
privacyContext
Indicates the situational or environmental conditions under which privacy-related actions, decisions, or data handling occur.
-
E.
hasSeclusion
chosen
Indicates that one entity provides, involves, or is characterized by a state or condition of privacy, isolation, or separation from others for 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a02f10505988190be5fd57566a90e0f |
completed | May 12, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_6a02f03a8c1481909e137e270119f7ef |
completed | May 12, 2026, 9:17 a.m. |
Created at: May 1, 2026, 1:53 a.m.