Triple
T321133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Ornithologists' Union |
E6417
|
entity |
| Predicate | hasFocusRegion |
P285
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [International Ornithologists' Union, hasFocusRegion, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFocusRegion Context triple: [International Ornithologists' Union, hasFocusRegion, worldwide]
-
A.
hasPrimaryFocus
Indicates that something is the main subject, concern, or area of attention for an entity or activity.
-
B.
hasCollectionFocus
Indicates that something is primarily concerned with, centered on, or directed toward a particular collection or set of items.
-
C.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
E.
mayProvideFocus
Indicates that one entity can potentially direct attention, emphasis, or concentration toward another entity or aspect.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea8047c08190872c875e00f6e7dd |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e946607081909c8b97473aaf8d1b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.