Triple
T8236368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehran Municipality |
E192416
|
entity |
| Predicate | capitalCityOfCountryGoverned |
P8146
|
FINISHED |
| Object | capital of Iran |
—
|
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: capital of Iran | Statement: [Tehran Municipality, capitalCityOfCountryGoverned, capital of Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityOfCountryGoverned Context triple: [Tehran Municipality, capitalCityOfCountryGoverned, capital of Iran]
-
A.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
B.
capitalCityOfCountry
chosen
Indicates that a city serves as the official capital of a specified country.
-
C.
capitalCityResidenceOf
Indicates that a person or entity resides in the capital city of a specified country or region.
-
D.
governingTerritorialCapital
Indicates that a territorial entity serves as the administrative or political capital for a governing body or jurisdiction.
-
E.
capitalLocation
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782a5e18819096235679f5a644a8 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.