Triple
T28161638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Xiao of Qin |
E714911
|
entity |
| Predicate | centralizedPower |
P22876
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Duke Xiao of Qin, centralizedPower, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralizedPower Context triple: [Duke Xiao of Qin, centralizedPower, yes]
-
A.
centralization
Indicates that control, authority, or decision-making power is concentrated in a single central entity rather than distributed among multiple entities.
-
B.
centralizesControlOf
Indicates that one entity consolidates and concentrates decision-making authority or governance power over another entity or set of entities.
-
C.
mainCentralPower
Indicates that an entity functions as the primary central authority or dominant power within a given system or context.
-
D.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
E.
positionOnCentralization
chosen
Indicates the degree to which an entity favors centralized versus decentralized control, authority, or decision-making.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 10:06 p.m.