Triple
T31904144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantabrian brown bear conservation area |
E814502
|
entity |
| Predicate | mainProtects |
P1040
|
FINISHED |
| Object | Cantabrian brown bear |
—
|
NE NERFINISHED |
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: Cantabrian brown bear | Statement: [Cantabrian brown bear conservation area, mainProtects, Cantabrian brown bear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainProtects Context triple: [Cantabrian brown bear conservation area, mainProtects, Cantabrian brown bear]
-
A.
laterProtects
Indicates that one entity provides protection for another entity at a later point in time than some referenced event or protection.
-
B.
protects
chosen
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
C.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
-
E.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, midnight