Triple
T28339445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Qingxiang of Chu |
E717768
|
entity |
| Predicate | powerStatusOfChu |
P86001
|
FINISHED |
| Object | declining regional power |
—
|
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: declining regional power | Statement: [King Qingxiang of Chu, powerStatusOfChu, declining regional power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerStatusOfChu Context triple: [King Qingxiang of Chu, powerStatusOfChu, declining regional power]
-
A.
powerStatus
Indicates whether an entity is currently powered on, off, or in another defined power state.
-
B.
deFactoPowerStatus
chosen
Indicates the actual, practical power or authority status an entity holds in reality, regardless of its formal or legally recognized position.
-
C.
powerCondition
Indicates that one entity’s ability to function, operate, or exert influence depends on a specified power-related requirement or state being satisfied.
-
D.
hasPowerSupplyType
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
E.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 12:38 a.m.