Triple
T34685770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Lie of Zhou |
E890741
|
entity |
| Predicate | royalHouseStatus |
P179625
|
FINISHED |
| Object | weakened central authority |
—
|
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: weakened central authority | Statement: [King Lie of Zhou, royalHouseStatus, weakened central authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalHouseStatus Context triple: [King Lie of Zhou, royalHouseStatus, weakened central authority]
-
A.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
B.
reigningRoyalHouseOf
Indicates that a particular royal house currently holds the ruling monarchy over a specified realm or country.
-
C.
relatedRoyalHouse
Indicates a relationship where one royal house is historically, genealogically, or politically connected to another royal house.
-
D.
royalHouseType
Indicates the specific kind or category of royal house associated with an entity (e.g., dynasty, ruling family type, or royal lineage classification).
-
E.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234cdb9c8190a6a46242de1b3926 |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:05 a.m.