Triple
T27606967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barisal Airport |
E700206
|
entity |
| Predicate | hasConnectivityType |
P95604
|
FINISHED |
| Object | domestic air connectivity |
—
|
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: domestic air connectivity | Statement: [Barisal Airport, hasConnectivityType, domestic air connectivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectivityType Context triple: [Barisal Airport, hasConnectivityType, domestic air connectivity]
-
A.
hasNoConnectionType
Indicates that there is explicitly no defined type or category of connection between the related entities.
-
B.
connectivityMode
chosen
Indicates how two or more entities are linked or able to communicate with each other, such as the type or method of connection used between them.
-
C.
canUseNetworkType
Indicates that an entity is permitted or able to operate using a specified type of network.
-
D.
hasGlobalNetworkType
Indicates that an entity is associated with a specific type or category of global network.
-
E.
hasCommunityNetworkType
Indicates the type or category of community network associated with an entity.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: April 27, 2026, 2:10 p.m.