Triple
T8558186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tebicuary River |
E202627
|
entity |
| Predicate | countryCapitalRegionRelation |
P35164
|
FINISHED |
| Object | located south of Asunción |
—
|
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: located south of Asunción | Statement: [Tebicuary River, countryCapitalRegionRelation, located south of Asunción]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCapitalRegionRelation Context triple: [Tebicuary River, countryCapitalRegionRelation, located south of Asunción]
-
A.
countryCapitalRegion
chosen
Indicates that a specified region is the capital region (administrative capital area) of a given country.
-
B.
countryCapitalOfRegion
Indicates that a country serves as the capital or primary governing state for a specified region.
-
C.
countryCapitalRelation
Indicates that one entity is the capital city of the country represented by the other entity.
-
D.
countryCapitalDistrict
Indicates that a specified district serves as the capital district (administrative capital area) of a given country.
-
E.
capitalCityOfRegion
Indicates that a city serves as the official capital of a specified region, functioning as its primary administrative or governmental center.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9485dd88190bc2cf2adf39d48ee |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.