Triple
T27147742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feni |
E681995
|
entity |
| Predicate | divisionCapitalDistance |
P122332
|
FINISHED |
| Object | Distance to Chattogram city |
—
|
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: Distance to Chattogram city | Statement: [Feni, divisionCapitalDistance, Distance to Chattogram city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionCapitalDistance Context triple: [Feni, divisionCapitalDistance, Distance to Chattogram city]
-
A.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
regionCapitalDistanceRelation
Indicates a relationship specifying the distance between a region and its capital.
-
C.
countryCapitalDistrict
Indicates that a specified district serves as the capital district (administrative capital area) of a given country.
-
D.
distanceFromRegionalCapital
chosen
Indicates the measured spatial distance between a given place and its corresponding regional capital.
-
E.
regionCapitalConnected
Indicates that a capital city is directly connected (e.g., by transport or infrastructure) to its surrounding region.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 9:12 a.m.