Triple

T5770462
Position Surface form Disambiguated ID Type / Status
Subject Katz v. United States E127318 entity
Predicate keyTestName P18903 FINISHED
Object two-prong reasonable expectation of privacy test 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: two-prong reasonable expectation of privacy test | Statement: [Katz v. United States, keyTestName, two-prong reasonable expectation of privacy test]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: keyTestName
Context triple: [Katz v. United States, keyTestName, two-prong reasonable expectation of privacy test]
  • A. testName chosen
    Indicates that an entity is identified or labeled by a specific test name.
  • B. keyOfSuite1
    Indicates that something is the primary key or identifying key associated with a particular suite (e.g., a suite of items, rooms, or data records).
  • C. keyText
    Indicates that a piece of text functions as a key or identifier used to access, reference, or unlock something in a system or context.
  • D. keyType
    Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
  • E. key
    Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over 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_69c00834f6308190851b0abeddd8ed7e completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02acb12c081908e4beee4a957f9f9 completed March 22, 2026, 5:45 p.m.
PD Predicate disambiguation batch_69c021ce8d3c81909b332cb1c33a61ad completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:50 p.m.