Triple
T35870345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prohibition in North America |
E1037204
|
entity |
| Predicate | eventuallyResultedIn |
P59870
|
FINISHED |
| Object | repeal of national prohibition laws |
—
|
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: repeal of national prohibition laws | Statement: [Prohibition in North America, eventuallyResultedIn, repeal of national prohibition laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventuallyResultedIn Context triple: [Prohibition in North America, eventuallyResultedIn, repeal of national prohibition laws]
-
A.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
eventuallyIn
Indicates that one entity will, at some later time or in the long run, come to be located in, belong to, or be contained within another entity or state.
-
C.
extendedAsResultOf
Indicates that one entity is prolonged, lengthened, or continued as a direct consequence of another event, condition, or action.
-
D.
collapseResultedIn
Indicates that a collapse event caused or led directly to a particular outcome or consequence.
-
E.
wasSubsequently
Indicates that one event, state, or action occurred after another in time, establishing a subsequent temporal relationship between them.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.