Triple
T26572184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelton v. Tucker |
E666854
|
entity |
| Predicate | freedomImpacted |
P160652
|
FINISHED |
| Object | freedom of association |
—
|
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: freedom of association | Statement: [Shelton v. Tucker, freedomImpacted, freedom of association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freedomImpacted Context triple: [Shelton v. Tucker, freedomImpacted, freedom of association]
-
A.
guaranteesFreedomTo
Indicates that one entity ensures or secures another entity’s ability or right to act freely.
-
B.
politicalFreedom
Indicates the degree to which an entity allows or experiences rights to participate in political processes, express political views, and choose or influence governance without coercion or repression.
-
C.
freedomCondition
Indicates the conditions or circumstances under which an entity is considered free or granted freedom.
-
D.
positionOnFreedom
Indicates a stance or viewpoint an entity holds regarding the concept, extent, or conditions of freedom.
-
E.
censorshipConsequence
Indicates the outcome or impact that results from an act or policy of censorship being applied.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614a519f0819087c98f8b48d14cce |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:58 a.m.