Triple
T21493835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of the Netherlands in Jakarta |
E530303
|
entity |
| Predicate | capitalCityEmbassy |
P122941
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Embassy of the Netherlands in Jakarta, capitalCityEmbassy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityEmbassy Context triple: [Embassy of the Netherlands in Jakarta, capitalCityEmbassy, yes]
-
A.
capitalLocation
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic entity.
-
B.
capitalCityResidenceOf
Indicates that a person or entity resides in the capital city of a specified country or region.
-
C.
capitalCityOfCountry
Indicates that a city serves as the official capital of a specified country.
-
D.
capitalAreaOf
Indicates that a specified area value represents the total land or geographic size of the capital city of a given entity.
-
E.
capitalCityBuildingOf
chosen
Indicates that a building is located in and associated with the capital city 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea567244819091863350fedae3ae |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:23 p.m.