Triple
T23041875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Latitude |
E573757
|
entity |
| Predicate | hasPrivacyConcern |
P15698
|
FINISHED |
| Object | location tracking |
—
|
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: location tracking | Statement: [Google Latitude, hasPrivacyConcern, location tracking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrivacyConcern Context triple: [Google Latitude, hasPrivacyConcern, location tracking]
-
A.
privacyProperty
chosen
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.
hasConfidentialityObligation
Indicates that an entity is bound by a duty to keep certain information secret and not disclose it to unauthorized parties.
-
E.
hasSecurityConsideration
Indicates that there is a relevant security-related issue, risk, or precaution associated with the referenced 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18513fc54819096d761a0be75b774 |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.