Triple

T7931614
Position Surface form Disambiguated ID Type / Status
Subject Google Glass E184200 entity
Predicate privacyConcerns P15689 FINISHED
Object public recording without consent 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 recording without consent | Statement: [Google Glass, privacyConcerns, public recording without consent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: privacyConcerns
Context triple: [Google Glass, privacyConcerns, public recording without consent]
  • 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. relatedSecurity
    Indicates that one security has a defined relationship or association with another security, such as dependency, linkage, or relevance.
  • D. concernsClause
    Indicates that one entity (such as a document, statement, or discussion) is about, relates to, or addresses a particular clause.
  • E. concernsRight
    Indicates that something is about or relates specifically to a legal or moral right held by an 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_69ca8290c21c8190906a5ca6fe2b03c4 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3ace87f081908635769942645e78 completed March 31, 2026, 3:09 a.m.
PD Predicate disambiguation batch_69cae9335f288190ba96781fd6576a2b completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 5:07 p.m.