Triple
T6177375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xijing |
E137853
|
entity |
| Predicate | usedAsCapitalDuring |
P52037
|
FINISHED |
| Object | multiple Chinese dynasties |
—
|
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: multiple Chinese dynasties | Statement: [Xijing, usedAsCapitalDuring, multiple Chinese dynasties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCapitalDuring Context triple: [Xijing, usedAsCapitalDuring, multiple Chinese dynasties]
-
A.
usedForCapitalOf
chosen
Indicates that something serves as the capital city or primary administrative center of a specified political or geographic entity.
-
B.
usedAsCurrency
Indicates that something functions as money or a medium of exchange within an economic system.
-
C.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
E.
hasCapitalDuringProcess
Indicates that an entity possesses or controls capital (financial or resource assets) throughout the duration of a specified process or activity.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc87bc48190834042d9c41d5b86 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.