Triple
T34178332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunkar |
E876736
|
entity |
| Predicate | locationOfIntroduction |
P29854
|
FINISHED |
| Object | Almaty |
E50745
|
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: Almaty | Statement: [Sunkar, locationOfIntroduction, Almaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfIntroduction Context triple: [Sunkar, locationOfIntroduction, Almaty]
-
A.
introducedFromLocation
Indicates that something or someone was brought, initiated, or first made present starting from a specified location.
-
B.
introductionLocation
chosen
Indicates the place or setting where an introduction or initial presentation of something or someone occurs.
-
C.
placeOfFirstPopularity
Indicates the location where something (such as a work, idea, or person) first gained notable recognition or widespread popularity.
-
D.
firstKnownLocationOnEarth
Indicates the earliest known place on Earth where the entity was present, discovered, or recorded.
-
E.
createdAtLocation
Indicates the place or location where an entity was originally created or brought into existence.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
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_6a36f9b3ee148190881bc9e254043b39 |
completed | June 20, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:54 a.m.