Triple
T38661940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jianzhou |
E940355
|
entity |
| Predicate | capitalOfRelatedPolity |
P197317
|
FINISHED |
| Object | Later Jin (early power base) |
—
|
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: Later Jin (early power base) | Statement: [Jianzhou, capitalOfRelatedPolity, Later Jin (early power base)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfRelatedPolity Context triple: [Jianzhou, capitalOfRelatedPolity, Later Jin (early power base)]
-
A.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
B.
capitalOfGoverningCountry
Indicates that a city serves as the capital of the country that governs a given territory or region.
-
C.
capitalOfCountryRuled
Indicates that a city serves as the capital of a country that is (or was) governed by a specified ruler or ruling entity.
-
D.
capitalOfLeadingPower
Indicates that one entity is the capital city of a dominant or leading political, economic, or military power.
-
E.
destinationCapitalOf
Indicates that a location serves as the capital city of the specified destination or region.
- F. None of above. chosen
Provenance (4 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
| PDg | Predicate description generation | batch_69fe86c98d688190a99d5dcb14e2dc95 |
completed | May 9, 2026, 12:58 a.m. |
Created at: May 3, 2026, 4:33 p.m.