Triple
T23744490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longshou Plateau |
E586775
|
entity |
| Predicate | functionDuringTangDynasty |
P153533
|
FINISHED |
| Object | imperial palace platform |
—
|
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: imperial palace platform | Statement: [Longshou Plateau, functionDuringTangDynasty, imperial palace platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuringTangDynasty Context triple: [Longshou Plateau, functionDuringTangDynasty, imperial palace platform]
-
A.
functionInMingDynasty
Indicates that an entity held an official role, position, or function during the Ming Dynasty.
-
B.
functionInQingDynasty
Indicates that an entity held a particular official role, position, or function during the Qing Dynasty.
-
C.
compiledUnderDynasty
Indicates that a work or document was compiled during the reign or period of a specific dynasty.
-
D.
functionDuringImperialEra
Indicates that a function, role, or activity occurred or was in effect during the imperial era.
-
E.
functionDuringReign
Indicates that a function, role, or activity occurred or was performed during the time span of a particular ruler’s reign.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcbcc4f88190a00fceeafbfb5cfd |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:12 p.m.