Triple
T10479693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | toxaphene |
E247137
|
entity |
| Predicate | bannedForUse |
P30858
|
FINISHED |
| Object | agricultural purposes in many 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: agricultural purposes in many countries | Statement: [toxaphene, bannedForUse, agricultural purposes in many countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bannedForUse Context triple: [toxaphene, bannedForUse, agricultural purposes in many countries]
-
A.
bannedBy
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another entity.
-
B.
bannedInContextOf
Indicates that something is prohibited or not allowed specifically within a particular situation, setting, or scope.
-
C.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
D.
restrictedFromUseFor
chosen
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
E.
bannedInCountry
Indicates that something is officially prohibited or not allowed within the jurisdiction of a specified country.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095b2ec881909e1220d83e750a75 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:22 p.m.