Triple
T31402629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tryggelev Nor nature reserve |
E801039
|
entity |
| Predicate | primaryProtectionTarget |
P9903
|
FINISHED |
| Object | birds |
—
|
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: birds | Statement: [Tryggelev Nor nature reserve, primaryProtectionTarget, birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryProtectionTarget Context triple: [Tryggelev Nor nature reserve, primaryProtectionTarget, birds]
-
A.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
B.
primarilyProtected
Indicates that one entity serves as the main or primary protector or safeguard for another entity.
-
C.
primaryTargetType
chosen
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
D.
protectionObjective
Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
-
E.
coreProtection
Indicates that an entity provides essential safeguarding or defense for another entity’s central or most critical component.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:20 p.m.