Triple
T28904170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outer Party |
E733029
|
entity |
| Predicate | forbiddenPractice |
P43576
|
FINISHED |
| Object | independent thought |
—
|
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: independent thought | Statement: [Outer Party, forbiddenPractice, independent thought]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forbiddenPractice Context triple: [Outer Party, forbiddenPractice, independent thought]
-
A.
condemnedPractice
Indicates that a particular practice is judged to be morally, legally, or socially unacceptable and is explicitly disapproved or denounced.
-
B.
excludedPractice
chosen
Indicates that a particular practice, behavior, or activity is explicitly not allowed, permitted, or covered within a given context or agreement.
-
C.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
D.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
E.
endedPracticeOf
Indicates that one entity caused another entity to stop or discontinue a particular practice or activity.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ad948748190abe57197575a19dc |
completed | May 2, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:05 a.m.