Triple
T34442335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Dorset Airport |
E884129
|
entity |
| Predicate | previousCommunityName |
P130357
|
FINISHED |
| Object | Cape Dorset |
—
|
NE NERFINISHED |
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: Cape Dorset | Statement: [Cape Dorset Airport, previousCommunityName, Cape Dorset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousCommunityName Context triple: [Cape Dorset Airport, previousCommunityName, Cape Dorset]
-
A.
formerCommunity
chosen
Indicates that an entity previously belonged to or was part of a particular community but is no longer a member of it.
-
B.
coreCommunity
Indicates that an entity belongs to the central or most essential group within a larger community.
-
C.
traditionalCommunityOf
Indicates that one entity is the customary or historically rooted community associated with, originating from, or traditionally linked to another entity.
-
D.
originCommunity
Indicates the community, group, or locality from which an entity originally comes or is derived.
-
E.
centralCommunityFor
Indicates that one entity serves as the primary hub or focal community for another entity or group.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 1, 2026, 2 a.m.