Triple
T31463109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tashkurgan Sarikoli |
E802655
|
entity |
| Predicate | hasSpeakerCommunityCenter |
P47569
|
FINISHED |
| Object | Tashkurgan town |
—
|
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: Tashkurgan town | Statement: [Tashkurgan Sarikoli, hasSpeakerCommunityCenter, Tashkurgan town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeakerCommunityCenter Context triple: [Tashkurgan Sarikoli, hasSpeakerCommunityCenter, Tashkurgan town]
-
A.
hasSpeakerCommunityStatus
Indicates that an entity has a particular status or role within a community of speakers of a language.
-
B.
hasCommunityCentre
chosen
Indicates that a place or area possesses or is served by a community centre facility.
-
C.
hasSpeakersIn
Indicates that an entity (such as an event, conference, or session) includes or is associated with speakers located in or belonging to a specified place or group.
-
D.
haveSpeakerPopulation
Indicates that an entity has a specified number or population size of people who speak a particular language.
-
E.
hasSpeakerIn
Indicates that an event, work, or communication features a particular entity serving as its speaker.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 30, 2026, 9:21 p.m.