Triple
T26405212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiankang |
E663812
|
entity |
| Predicate | timeAsMajorCapital |
P20655
|
FINISHED |
| Object | 3rd century to 6th century |
—
|
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: 3rd century to 6th century | Statement: [Jiankang, timeAsMajorCapital, 3rd century to 6th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAsMajorCapital Context triple: [Jiankang, timeAsMajorCapital, 3rd century to 6th century]
-
A.
timeAsCapital
chosen
Indicates the period during which a particular city served as the capital of a political entity.
-
B.
timeInCapital
Indicates that a specified amount of time is spent or occurs within the capital city of a given political or administrative entity.
-
C.
capitalOrMajorCenter
Indicates that a location serves as a capital city or a primary major center (political, economic, or cultural hub) for a larger region or entity.
-
D.
countryCapitalUntil
Indicates that a specified city served as the capital of a given country up to (but not necessarily including) a particular end date or time period.
-
E.
hasCapitalCityUsingTime
Indicates that an entity has a capital city that is valid or in effect during a specified time period.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610f727ac819099df3683c15dc6cc |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 11:34 p.m.