Triple
T3962801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmopan |
E85942
|
entity |
| Predicate | isPlannedInlandCapital |
P36957
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Belmopan, isPlannedInlandCapital, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlannedInlandCapital Context triple: [Belmopan, isPlannedInlandCapital, true]
-
A.
isPlannedRegionalCapitalOf
Indicates that a location has been officially designated to become the regional capital in the future, but is not yet serving as the current regional capital.
-
B.
isPlannedCity
chosen
Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
-
C.
isInlandCity
Indicates that a city is located away from the coast, without direct access to the sea or ocean.
-
D.
isDiplomaticCenterOf
Indicates that a location serves as the primary site or hub for conducting diplomatic activities and relations for a specified entity.
-
E.
isNationalAdministrativeCenter
Indicates that a location serves as the primary administrative or governmental center for a nation.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.