Triple
T3060891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Important Bird Area |
E61992
|
entity |
| Predicate | notNecessarily |
P32731
|
FINISHED |
| Object | legally protected |
—
|
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: legally protected | Statement: [Important Bird Area, notNecessarily, legally protected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notNecessarily Context triple: [Important Bird Area, notNecessarily, legally protected]
-
A.
notTypically
Indicates that the referenced situation, behavior, or relationship does not usually or normally occur under standard or expected conditions.
-
B.
notGuaranteed
chosen
Indicates that the specified outcome, condition, or obligation is not assured to occur or be fulfilled.
-
C.
ultimatelyDoesNot
Indicates that, despite any preceding conditions or possibilities, the referenced entity or action does not in the end occur, hold, or get carried out.
-
D.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
notStronglyAssociatedWith
Indicates that two entities have little to no meaningful or statistically significant relationship or connection with each other.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e9e1e248190b5ed5ebcdad1321e |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.