Triple
T17479996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone v. Graham |
E425630
|
entity |
| Predicate | foundSecularPurpose |
P127615
|
FINISHED |
| Object | lacking |
—
|
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: lacking | Statement: [Stone v. Graham, foundSecularPurpose, lacking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundSecularPurpose Context triple: [Stone v. Graham, foundSecularPurpose, lacking]
-
A.
hasSecularUse
Indicates that something is used in a non-religious, worldly, or secular context or purpose.
-
B.
cultPurpose
Indicates that an entity (such as a cult, group, or organization) exists or operates with a specific overarching purpose, goal, or objective.
-
C.
findsPurposeThrough
Indicates that one entity derives its sense of purpose, meaning, or fulfillment through its relationship with or actions involving another entity.
-
D.
hasSecularAspects
Indicates that something includes or exhibits non-religious, worldly, or secular characteristics or dimensions.
-
E.
traditionalPurpose
Indicates that something serves a role, function, or use that is established by long-standing custom or tradition.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bf1e8081909f4d4b8992412e62 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:48 a.m.