Triple
T26071636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monviso Transboundary Biosphere Reserve |
E657562
|
entity |
| Predicate | hasKeySpeciesHabitat |
P164660
|
FINISHED |
| Object | alpine flora |
—
|
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: alpine flora | Statement: [Monviso Transboundary Biosphere Reserve, hasKeySpeciesHabitat, alpine flora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeySpeciesHabitat Context triple: [Monviso Transboundary Biosphere Reserve, hasKeySpeciesHabitat, alpine flora]
-
A.
containsSpeciesWithHabitat
Indicates that an entity includes one or more species that are associated with a particular habitat.
-
B.
hasAssociatedHabitat
Indicates that an entity is linked to a particular habitat in which it typically lives, occurs, or is found.
-
C.
habitatOfNotableSpecies
chosen
Indicates that a location serves as the natural environment or living area for one or more notable species.
-
D.
hasScientificSpecies
Indicates that an entity is associated with a specific scientific (Latin) species name.
-
E.
hasCommonSpecies
Indicates that two entities share at least one species in common.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 26, 2026, 7:29 p.m.