Triple
T3060905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Important Bird Area |
E61992
|
entity |
| Predicate | dataUsedIn |
P25490
|
FINISHED |
| Object | international conservation policy |
—
|
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: international conservation policy | Statement: [Important Bird Area, dataUsedIn, international conservation policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataUsedIn Context triple: [Important Bird Area, dataUsedIn, international conservation policy]
-
A.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
B.
usedDataFrom
Indicates that one entity utilized or relied on data originating from another entity.
-
C.
usedDataAnalytics
Indicates that an entity applied data analytics techniques or insights in performing an action or making a decision related to another entity.
-
D.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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.