Triple
T29052633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Valley |
E735300
|
entity |
| Predicate | hasRareSpecies |
P22447
|
FINISHED |
| Object | Ethiopian wolf |
—
|
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: Ethiopian wolf | Statement: [Web Valley, hasRareSpecies, Ethiopian wolf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRareSpecies Context triple: [Web Valley, hasRareSpecies, Ethiopian wolf]
-
A.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
B.
hasNativeSpecies
Indicates that a particular species naturally occurs and evolved in a specified geographic area or habitat, rather than being introduced from elsewhere.
-
C.
hasBiodiversityFeature
chosen
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
D.
hasCommonSpecies
Indicates that two entities share at least one species in common.
-
E.
hasProtectedSpecies
Indicates that the subject contains, supports, or is associated with one or more species that are legally or formally designated as protected.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 10:09 a.m.