Triple
T896767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulysses |
E19362
|
entity |
| Predicate | banLiftedInUnitedStates |
P20841
|
FINISHED |
| Object | 1933 |
—
|
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: 1933 | Statement: [Ulysses, banLiftedInUnitedStates, 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: banLiftedInUnitedStates Context triple: [Ulysses, banLiftedInUnitedStates, 1933]
-
A.
allyOfUnitedStates
Indicates a relationship where an entity maintains a supportive, cooperative, or formally allied partnership with the United States.
-
B.
statusInUnitedStates
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
-
C.
conditionsLiftingOfSanctionsOn
Indicates that one entity specifies or determines the requirements under which sanctions imposed on another entity will be removed or relaxed.
-
D.
borderWithUnitedStatesVia
Indicates that one entity shares a border with the United States specifically through or along the second entity (such as a body of water, territory, or region).
-
E.
sponsorStates
Indicates that one entity acts as a sponsor or supporting state for another entity, typically providing backing, endorsement, or resources.
- F. None of above. chosen
Provenance (4 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad2550c88190a624eb5627d472ad |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4a38ec8190915916d80299ab55 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.