Triple
T28653223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Hill |
E725256
|
entity |
| Predicate | capitalOfCountryPoliticalCenter |
P37327
|
FINISHED |
| Object | Liberia |
—
|
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: Liberia | Statement: [Capitol Hill, capitalOfCountryPoliticalCenter, Liberia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfCountryPoliticalCenter Context triple: [Capitol Hill, capitalOfCountryPoliticalCenter, Liberia]
-
A.
capitalLocation
chosen
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.
capitalOfGoverningCountry
Indicates that a city serves as the capital of the country that governs a given territory or region.
-
D.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
E.
governingTerritorialCapital
Indicates that a territorial entity serves as the administrative or political capital for a governing body or jurisdiction.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 4:53 a.m.