Triple
T25440024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CGP |
E637477
|
entity |
| Predicate | locationDivision |
P110852
|
FINISHED |
| Object | Chittagong Division |
—
|
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: Chittagong Division | Statement: [CGP, locationDivision, Chittagong Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationDivision Context triple: [CGP, locationDivision, Chittagong Division]
-
A.
regionDivision
Indicates a hierarchical or organizational subdivision relationship where one region is partitioned into smaller constituent regions.
-
B.
geographicDivision
chosen
Indicates that one place is an administrative or territorial subdivision of another place.
-
C.
urbanDivisionRelation
Indicates a relationship where one urban area, zone, or administrative unit is divided into, or associated with, specific sub-areas or subdivisions within a city or metropolitan region.
-
D.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
-
E.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 21, 2026, 2 p.m.