Triple
T5770463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katz v. United States |
E127318
|
entity |
| Predicate | testProng |
P66319
|
FINISHED |
| Object | subjective expectation of privacy |
—
|
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: subjective expectation of privacy | Statement: [Katz v. United States, testProng, subjective expectation of privacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testProng Context triple: [Katz v. United States, testProng, subjective expectation of privacy]
-
A.
LemonTestProng
Indicates that a situation or government action satisfies a specific criterion (or “prong”) of the Lemon test used to evaluate whether it violates the Establishment Clause.
-
B.
hasProng
Indicates that one entity possesses, includes, or is equipped with a prong or prongs as part of its structure or design.
-
C.
hasNumberOfProngs
Indicates the relationship specifying how many prongs an object or entity possesses.
-
D.
testsPrinciple
Indicates that an entity evaluates, examines, or challenges the validity or applicability of a principle.
-
E.
testPilot
Indicates that an entity serves as a pilot responsible for testing and evaluating aircraft or related flight systems.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c02ac9603481909e3fa295d7904a15 |
completed | March 22, 2026, 5:45 p.m. |
Created at: March 22, 2026, 3:50 p.m.