Triple
T861404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Struggle |
E18604
|
entity |
| Predicate | bannedIn |
P4355
|
FINISHED |
| Object | various countries at different times |
—
|
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: various countries at different times | Statement: [My Struggle, bannedIn, various countries at different times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bannedIn Context triple: [My Struggle, bannedIn, various countries at different times]
-
A.
bannedBy
chosen
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another entity.
-
B.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
C.
isCriminalizedIn
Indicates that a specific behavior, action, or condition is prohibited and subject to legal penalties within a particular jurisdiction or legal system.
-
D.
usedInCountry
Indicates that something is utilized, applied, or in operation within the specified country.
-
E.
excludedFromAmnesty
Indicates that an entity is not eligible for, or is specifically denied, the benefits or protections granted by an amnesty.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac6631408190a19b83126fa86100 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.