Triple
T33790795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | camphechlor |
E865924
|
entity |
| Predicate | wasBannedForMostUsesIn |
P30858
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [camphechlor, wasBannedForMostUsesIn, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBannedForMostUsesIn Context triple: [camphechlor, wasBannedForMostUsesIn, United States]
-
A.
wasBannedAs
Indicates that an entity was prohibited or barred from participation, access, or activity in a specific role, capacity, or status.
-
B.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
C.
wasBannedDuring
Indicates that an entity was prohibited or barred from participation or access for the duration of a specified time period or event.
-
D.
isOftenProhibitedAt
Indicates that something is frequently not allowed or banned in a particular place, context, or situation.
-
E.
restrictedFromUseFor
chosen
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.