Triple
T34442398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CYTE |
E884130
|
entity |
| Predicate | hasCommunityCurrentName |
P195366
|
FINISHED |
| Object | Kinngait |
E884124
|
NE 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: Kinngait | Statement: [CYTE, hasCommunityCurrentName, Kinngait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityCurrentName Context triple: [CYTE, hasCommunityCurrentName, Kinngait]
-
A.
hasCurrentCommunityName
chosen
Indicates that an entity currently bears or is identified by a specific community name.
-
B.
currentName
Indicates the present or most recently assigned name associated with an entity.
-
C.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
D.
hasKeyCommunity
Indicates that an entity is associated with or belongs to a primary or central community that is especially important or influential for it.
-
E.
hasCurrentCoreCityName
Indicates that an entity is associated with its present or officially recognized core city name.
- F. None of above.
Provenance (4 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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37661438f081908114bed19686aa02 |
completed | June 21, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.