Triple
T28018006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laishevo District |
E707602
|
entity |
| Predicate | encompassesAreaServedBy |
P163629
|
FINISHED |
| Object | Kazan International Airport |
—
|
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: Kazan International Airport | Statement: [Laishevo District, encompassesAreaServedBy, Kazan International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encompassesAreaServedBy Context triple: [Laishevo District, encompassesAreaServedBy, Kazan International Airport]
-
A.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
B.
areaOfService
Indicates the geographic or functional region within which a service is provided or applicable.
-
C.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
D.
strategicAreaServed
Indicates that an entity provides services or exerts influence within a particular area considered strategically important.
-
E.
hasPrimaryServiceArea
Indicates that an entity is associated with a main geographic or functional area in which it primarily provides its services.
- F. None of above. chosen
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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c087c5c81908a4bda4294a61f1d |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:08 p.m.