Triple
T34442366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYTE |
E884130
|
entity |
| Predicate | hasFormerCommunityName |
P65
|
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: [CYTE, hasFormerCommunityName, Cape Dorset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerCommunityName Context triple: [CYTE, hasFormerCommunityName, Cape Dorset]
-
A.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
B.
containsFormerlyNamed
Indicates that one entity currently contains another entity that was previously known by a different name.
-
C.
heldAtFormerName
Indicates that an event or activity took place at a location when it was known by a previous or former name.
-
D.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
E.
hasFormerPartnerName
Indicates that an entity has the recorded name of a person or organization who was previously their partner.
- 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_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 1, 2026, 2 a.m.