Triple

T33908064
Position Surface form Disambiguated ID Type / Status
Subject white-rumped vulture E869237 entity
Predicate historicallyAbundantIn P201831 FINISHED
Object India 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: India | Statement: [white-rumped vulture, historicallyAbundantIn, India]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyAbundantIn
Context triple: [white-rumped vulture, historicallyAbundantIn, India]
  • A. historicallyObservedIn
    Indicates that something has been recorded or documented as occurring, existing, or taking place within a particular historical context, period, or location.
  • B. historicallyDominantIn
    Indicates that one entity has held a position of prevailing power, influence, or control over another entity or within a particular domain during a past historical period.
  • C. historicallyNativeTo
    Indicates that an entity has been originally or traditionally present in, or originating from, a particular place or region over a significant period in history.
  • D. historicallyInhabitedBy
    Indicates that a place or region was inhabited by a particular group or population during some period in the past.
  • E. historicallyBasedIn
    Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
  • 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_69f3499869bc8190b6c33a81686af226 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a0027e4a59481909417b2531daaf480 completed May 10, 2026, 6:38 a.m.
PD Predicate disambiguation batch_6a0026a42bc08190ad3322ce625a523a completed May 10, 2026, 6:33 a.m.
PDg Predicate description generation batch_6a0027e384d08190ad92a6a21c8f84b5 completed May 10, 2026, 6:38 a.m.
Created at: May 1, 2026, 1:48 a.m.