Triple

T59549
Position Surface form Disambiguated ID Type / Status
Subject Chamorro E1180 entity
Predicate endangeredStatus P1339 FINISHED
Object vulnerable language 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: vulnerable language | Statement: [Chamorro, endangeredStatus, vulnerable language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: endangeredStatus
Context triple: [Chamorro, endangeredStatus, vulnerable language]
  • A. conservationStatus chosen
    Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
  • B. hasEndemicSpecies
    Indicates that a place or region contains species that are native to and found only within that specific geographic area.
  • C. biodiversityStatus
    Indicates the current condition or level of biological diversity associated with an entity, often in terms of richness, health, or conservation concern.
  • D. hasProtectedAreaStatus
    Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
  • E. stateBird
    Indicates that a particular bird species is officially designated as the state bird of a given state or region.
  • 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_69a24a552ef88190a0df287d68c65cba completed Feb. 28, 2026, 1:52 a.m.
NER Named-entity recognition batch_69a250e401288190ba12322c9c5f07c9 completed Feb. 28, 2026, 2:20 a.m.
PD Predicate disambiguation batch_69a24e9f40908190a2f4a2111469b733 completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 1:55 a.m.