Triple

T18513815
Position Surface form Disambiguated ID Type / Status
Subject American beech E452407 entity
Predicate introducedPest P131963 FINISHED
Object beech scale insect 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: beech scale insect | Statement: [American beech, introducedPest, beech scale insect]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducedPest
Context triple: [American beech, introducedPest, beech scale insect]
  • A. notablePest
    Indicates that an entity is recognized as a significant or impactful pest, typically causing notable harm, damage, or nuisance.
  • B. introducedSpecies
    Indicates that a species has been brought by humans, intentionally or unintentionally, into an environment where it does not naturally occur.
  • C. cultIntroducedBy
    Indicates that a particular cult or religious practice was brought into a place, group, or culture through the agency or influence of a specific person or entity.
  • D. reintroducedSpecies
    Indicates that a species has been brought back and established again in an area where it had previously disappeared or been extirpated.
  • E. hasStateInsect
    Indicates that a state has designated a particular insect as its official state insect.
  • F. None of above. chosen

Provenance (4 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_69d8d386df84819092355ebb260d848e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53348274c8190a82861b0104538e3 completed April 19, 2026, 7:55 p.m.
PD Predicate disambiguation batch_69e469e0025c81908f16ed4f922674af completed April 19, 2026, 5:36 a.m.
PDg Predicate description generation batch_69e46d2b93bc8190a6070018d7046547 completed April 19, 2026, 5:50 a.m.
Created at: April 10, 2026, 11:36 a.m.