Triple
T32368325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Li clan of Tang |
E827058
|
entity |
| Predicate | secondaryCapitalDuringRule |
P48912
|
FINISHED |
| Object | Luoyang |
—
|
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: Luoyang | Statement: [Li clan of Tang, secondaryCapitalDuringRule, Luoyang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryCapitalDuringRule Context triple: [Li clan of Tang, secondaryCapitalDuringRule, Luoyang]
-
A.
secondaryCapital
chosen
Indicates that a location serves as an additional or secondary capital city for a political entity, alongside its primary capital.
-
B.
capitalRenamedTo
Indicates that a place’s status or name as a capital city has been changed to a new capital designation or name.
-
C.
capitalRenamedFrom
Indicates that a capital city previously had a different name, specifying the former name from which it was renamed.
-
D.
proposedCapital
Indicates that one entity has been suggested or nominated to serve as the capital of another entity (such as a country, state, or region), but this status may not yet be official or finalized.
-
E.
ruledCity
Indicates that a person or governing entity exercised political authority or control over a specific city.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 12:50 a.m.