Triple
T13079700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSD |
E310169
|
entity |
| Predicate | isIllegalIn |
P18713
|
FINISHED |
| Object | most countries |
—
|
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: most countries | Statement: [LSD, isIllegalIn, most countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIllegalIn Context triple: [LSD, isIllegalIn, most countries]
-
A.
declaredIllegalIn
Indicates that an authority has officially designated something as illegal within a specific jurisdiction or context.
-
B.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
C.
isCriminalizedIn
chosen
Indicates that a specific behavior, action, or condition is prohibited and subject to legal penalties within a particular jurisdiction or legal system.
-
D.
existsInJurisdiction
Indicates that an entity is located within, falls under, or is subject to the authority of a particular legal or administrative jurisdiction.
-
E.
hasLegalDefinitionIn
Indicates that something possesses an official legal definition within a specified legal source, system, or jurisdiction.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98119cb7081908b78ffe83ec99851 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:01 p.m.