Triple

T19186687
Position Surface form Disambiguated ID Type / Status
Subject planetary boundaries framework E469719 entity
Predicate originallyNamedBoundary P134778 FINISHED
Object biodiversity loss 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: biodiversity loss | Statement: [planetary boundaries framework, originallyNamedBoundary, biodiversity loss]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originallyNamedBoundary
Context triple: [planetary boundaries framework, originallyNamedBoundary, biodiversity loss]
  • A. boundaryName
    Indicates the designated name or label assigned to a specific boundary or border between entities.
  • B. previouslyPartOfBoundaryBetween
    Indicates that something once formed part of the dividing line or border between two areas or entities, but no longer does so.
  • C. boundaryIdentifiedWith
    Indicates that the boundary of one entity is treated as equivalent to, or merged with, the boundary of another entity.
  • D. isPartOfLargerBoundary
    Indicates that one boundary is contained within or forms a component of a larger encompassing boundary.
  • E. isBoundaryFor
    Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
  • 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_69d8dd0ad9088190a173b32657ae2e7a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f620f1f08190a0daaf0d1483d724 completed April 20, 2026, 9:47 a.m.
PD Predicate disambiguation batch_69e4b9bb158481909478ca2e06f3ba39 completed April 19, 2026, 11:17 a.m.
PDg Predicate description generation batch_69e4bfe9ef7081908a74a57d1fc731ea completed April 19, 2026, 11:43 a.m.
Created at: April 10, 2026, 12:07 p.m.