Triple
T28884727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciracas |
E732523
|
entity |
| Predicate | isPartOfCapitalCityRegion |
P149036
|
FINISHED |
| Object | Jakarta |
—
|
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: Jakarta | Statement: [Ciracas, isPartOfCapitalCityRegion, Jakarta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCapitalCityRegion Context triple: [Ciracas, isPartOfCapitalCityRegion, Jakarta]
-
A.
isPartOfCapitalCityOf
chosen
Indicates that something is a constituent or component of the capital city belonging to a particular political or administrative entity.
-
B.
hasCapitalRegionRelation
Indicates a relationship where one entity serves as the capital region or administrative capital area of another entity.
-
C.
belongsToMetropolitanRegion
Indicates that one geographic or administrative area is part of, or included within, a larger metropolitan region.
-
D.
partOfMetropolitanArea
Indicates that one place is included within and belongs to the larger metropolitan area of another place.
-
E.
capitalRegionIncluded
Indicates that a specified region contains or encompasses the capital area of a given political or administrative 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 28, 2026, 7:49 a.m.