Triple
T31103708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mentats |
E792739
|
entity |
| Predicate | prohibitionContext |
P72781
|
FINISHED |
| Object | ban on computers |
—
|
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: ban on computers | Statement: [Mentats, prohibitionContext, ban on computers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitionContext Context triple: [Mentats, prohibitionContext, ban on computers]
-
A.
prohibitionActivity
Indicates that a certain activity is forbidden or not allowed to be performed.
-
B.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
C.
bannedInContextOf
chosen
Indicates that something is prohibited or not allowed specifically within a particular situation, setting, or scope.
-
D.
drinkingContext
Indicates the situational or environmental circumstances under which a drinking event occurs (such as time, place, social setting, or purpose).
-
E.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.