Triple
T30889742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Consultation |
E786865
|
entity |
| Predicate | discouragesPractice |
P2184
|
FINISHED |
| Object | oppression |
—
|
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: oppression | Statement: [The Consultation, discouragesPractice, oppression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discouragesPractice Context triple: [The Consultation, discouragesPractice, oppression]
-
A.
discourages
chosen
Indicates an action or influence that deters, dissuades, or reduces the likelihood of someone performing a particular behavior or pursuing a certain outcome.
-
B.
condemnedPractice
Indicates that a particular practice is judged to be morally, legally, or socially unacceptable and is explicitly disapproved or denounced.
-
C.
discouragedUsageReason
Indicates the reason why a particular usage, action, or practice is considered discouraged.
-
D.
discouragedSince
Indicates that an entity has been experiencing discouragement continuously from a specified point in time onward.
-
E.
excludedPractice
Indicates that a particular practice, behavior, or activity is explicitly not allowed, permitted, or covered within a given context or agreement.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 8:49 p.m.