Triple
T3161277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall of Central Harmony |
E66105
|
entity |
| Predicate | ownershipHistorical |
P22003
|
FINISHED |
| Object | Chinese imperial household |
—
|
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: Chinese imperial household | Statement: [Hall of Central Harmony, ownershipHistorical, Chinese imperial household]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownershipHistorical Context triple: [Hall of Central Harmony, ownershipHistorical, Chinese imperial household]
-
A.
ownershipHistory
chosen
Indicates the sequence of past and present owners associated with an entity over time.
-
B.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
C.
historicallyControlledBy
Indicates that an entity was under the control, rule, or governance of another entity during some period in the past.
-
D.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
E.
sponsorHistory
Indicates that one entity has previously acted as a sponsor for another entity or event over time.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada617824c8190a293230041b2f1ea |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.