Triple
T25456383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mendesian Dynasty |
E637924
|
entity |
| Predicate | predecessorCityCapital |
P136630
|
FINISHED |
| Object | Mendes |
—
|
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: Mendes | Statement: [Mendesian Dynasty, predecessorCityCapital, Mendes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorCityCapital Context triple: [Mendesian Dynasty, predecessorCityCapital, Mendes]
-
A.
predecessorCityName
Indicates that the value is the name of the city that previously held a given role, status, or position before the current city.
-
B.
formerCapitalOf
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
-
C.
formerCapitalLocatedOn
Indicates that a city which once served as a capital is situated on or alongside a specified geographic feature, such as a river, coast, or lake.
-
D.
wasPrecededAsCapitalBy
chosen
Indicates that one entity served as a capital city immediately before another entity became the capital.
-
E.
formerNameOfCapital
Indicates that one entity was the previous official name of a capital city before it was renamed.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 2:09 p.m.