Triple
T7940051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merlin Bird ID |
E184365
|
entity |
| Predicate | supportsGeographicCoverage |
P54919
|
FINISHED |
| Object | multiple continents |
—
|
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: multiple continents | Statement: [Merlin Bird ID, supportsGeographicCoverage, multiple continents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGeographicCoverage Context triple: [Merlin Bird ID, supportsGeographicCoverage, multiple continents]
-
A.
geographicAreaOfSupport
chosen
Indicates the geographic region or area within which support, assistance, or services are provided or applicable.
-
B.
containsGeographicalArea
Indicates that one geographical area spatially encompasses or includes another geographical area within its boundaries.
-
C.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
-
D.
hasLandCoverage
Indicates that a specified area or region is covered or occupied by a particular type of land surface or land use.
-
E.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0983388190a77e8d5d899c5130 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.