Triple
T32656658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maniilaq Health Center |
E834879
|
entity |
| Predicate | ruralDesignation |
P2460
|
FINISHED |
| Object | remote Arctic region facility |
—
|
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: remote Arctic region facility | Statement: [Maniilaq Health Center, ruralDesignation, remote Arctic region facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruralDesignation Context triple: [Maniilaq Health Center, ruralDesignation, remote Arctic region facility]
-
A.
isRural
chosen
Indicates that something is located in, characteristic of, or associated with a countryside or non-urban area.
-
B.
hasAgriculturalDesignation
Indicates that an entity is assigned a specific agricultural classification, status, or use designation.
-
C.
isInRuralAreaOf
Indicates that one entity is located within the rural area or countryside region associated with another entity.
-
D.
hasRuralZoningCharacter
Indicates that a property or area possesses zoning attributes and regulations typical of rural land use.
-
E.
isRuralRegion
Indicates that a region is classified as rural, typically characterized by low population density and limited urban development.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c77c972081908d51fa8a9f927b12 |
completed | May 3, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:08 a.m.