Triple
T29900109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradox Engine |
E759385
|
entity |
| Predicate | isBannedIn |
P72781
|
FINISHED |
| Object | Commander |
—
|
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: Commander | Statement: [Paradox Engine, isBannedIn, Commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBannedIn Context triple: [Paradox Engine, isBannedIn, Commander]
-
A.
bannedInCountry
Indicates that something is officially prohibited or not allowed within the jurisdiction of a specified country.
-
B.
bannedInContextOf
chosen
Indicates that something is prohibited or not allowed specifically within a particular situation, setting, or scope.
-
C.
bannedBy
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another entity.
-
D.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
E.
isBarred
Indicates that an entity is officially prohibited or excluded from participating in, entering, or accessing another entity 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6772e14d48190a9c4dda3d35d0f37 |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:06 p.m.