Triple
T32703706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trischen |
E836211
|
entity |
| Predicate | birdProtection |
P46327
|
FINISHED |
| Object | important breeding area |
—
|
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: important breeding area | Statement: [Trischen, birdProtection, important breeding area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birdProtection Context triple: [Trischen, birdProtection, important breeding area]
-
A.
supportsBirdlife
Indicates that one entity provides conditions or resources that help sustain or benefit bird life associated with another entity.
-
B.
birdwatchingFeature
Indicates a feature, characteristic, or amenity that is specifically related to or beneficial for birdwatching activities.
-
C.
birdDiversity
Indicates the variety and richness of different bird species present within a given area, community, or dataset.
-
D.
supportsWildlife
chosen
Indicates that one entity provides conditions, resources, or protection that help sustain or benefit wildlife associated with another entity.
-
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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c84fd3d48190aae000560ca4f764 |
completed | May 3, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:10 a.m.