Triple
T13019141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Key Biodiversity Area |
E322629
|
entity |
| Predicate | identifiedUsing |
P107472
|
FINISHED |
| Object | quantitative thresholds |
—
|
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: quantitative thresholds | Statement: [Key Biodiversity Area, identifiedUsing, quantitative thresholds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiedUsing Context triple: [Key Biodiversity Area, identifiedUsing, quantitative thresholds]
-
A.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
B.
identificationType
Indicates the specific kind or category of identification associated with an entity or relationship.
-
C.
identityStatus
Indicates the current state or condition of an entity’s identity, such as whether it is verified, active, pending, or otherwise classified.
-
D.
identityRevealedIn
Indicates that an entity’s true identity becomes known or disclosed within a specified context, source, or situation.
-
E.
identityConcept
Indicates that two concepts are the same in identity, representing exactly the same underlying idea or meaning.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ece22908190a0941e23df7c774d |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:51 p.m.