Triple

T10129674
Position Surface form Disambiguated ID Type / Status
Subject Enterprise, Alabama E226302 entity
Predicate respondedToBollWeevilBy P17295 FINISHED
Object diversifying crops to peanuts 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: diversifying crops to peanuts | Statement: [Enterprise, Alabama, respondedToBollWeevilBy, diversifying crops to peanuts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: respondedToBollWeevilBy
Context triple: [Enterprise, Alabama, respondedToBollWeevilBy, diversifying crops to peanuts]
  • A. hasOppositionResponse
    Indicates that an entity has issued or expressed a response opposing, challenging, or objecting to another entity, action, or proposal.
  • B. establishedInResponseTo chosen
    Indicates that something was created, initiated, or set up as a direct reaction to a specific event, condition, or stimulus.
  • C. hasStateInsect
    Indicates that a state has designated a particular insect as its official state insect.
  • D. enactedInResponseTo
    Indicates that one action, policy, or measure was carried out as a direct reaction to a specific prior event, condition, or stimulus.
  • E. answeredBy
    Indicates that a question, request, or problem is responded to or resolved by a particular entity.
  • 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_69ca843057b48190a86730167f5d6b98 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cdd333186c819088bbf617967f24fa completed April 2, 2026, 2:23 a.m.
PD Predicate disambiguation batch_69cd4ba1d360819087698d04a53cc87e completed April 1, 2026, 4:45 p.m.
Created at: March 30, 2026, 9:05 p.m.