Triple
T19628381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruwanwella |
E471197
|
entity |
| Predicate | districtSubdivisionType |
P79356
|
FINISHED |
| Object | district |
—
|
LITERAL 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: district | Statement: [Ruwanwella, districtSubdivisionType, district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: districtSubdivisionType Context triple: [Ruwanwella, districtSubdivisionType, district]
-
A.
subdivisionType0
Indicates that the referenced entity is classified as the primary (level 0) type of administrative or territorial subdivision within a larger jurisdiction.
-
B.
subdivisionOfJurisdiction
Indicates that one jurisdiction is a smaller administrative or territorial unit that forms part of a larger jurisdiction.
-
C.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
D.
citySubdivision
Indicates that one administrative or geographic unit is a smaller subdivision contained within a larger city.
-
E.
politicalSubdivisionType
chosen
Indicates the specific category or level of governmental or administrative division that characterizes a political subdivision.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641007e5881908da78e50aa36f340 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.