Triple
T21630751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Maria, Bulacan |
E533821
|
entity |
| Predicate | countryCapitalRegionProximity |
P33891
|
FINISHED |
| Object | near National Capital Region |
—
|
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: near National Capital Region | Statement: [Santa Maria, Bulacan, countryCapitalRegionProximity, near National Capital Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCapitalRegionProximity Context triple: [Santa Maria, Bulacan, countryCapitalRegionProximity, near National Capital Region]
-
A.
countryCapitalNearby
chosen
Indicates that a country’s capital city is geographically close to a specified location or entity.
-
B.
regionCapitalNearby
Indicates that a capital city of a region is located close to the referenced place or entity.
-
C.
countryCapitalRegion
Indicates that a specified region is the capital region (administrative capital area) of a given country.
-
D.
regionCapitalDistanceRelation
Indicates a relationship specifying the distance between a region and its capital.
-
E.
countryCapitalDistrict
Indicates that a specified district serves as the capital district (administrative capital area) of a given country.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef521679fc81909c94d42439fda4ba |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.