Triple
T1584817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemon v. Kurtzman |
E34039
|
entity |
| Predicate | LemonTestProng |
P32894
|
FINISHED |
| Object | government action must have a secular legislative purpose |
—
|
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: government action must have a secular legislative purpose | Statement: [Lemon v. Kurtzman, LemonTestProng, government action must have a secular legislative purpose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LemonTestProng Context triple: [Lemon v. Kurtzman, LemonTestProng, government action must have a secular legislative purpose]
-
A.
establishesTest
Indicates that an entity creates or sets up a test or testing procedure for another entity.
-
B.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
-
C.
centralTest
Indicates that an entity serves as the primary or core test within a set of tests or an evaluation process.
-
D.
commonTest
Indicates that two or more entities share the same test, testing procedure, or evaluation in common.
-
E.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69abacf991148190b20521c063f93bfd |
completed | March 7, 2026, 4:43 a.m. |
Created at: March 4, 2026, 7:27 p.m.