Triple
T27959460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Cao |
E704538
|
entity |
| Predicate | roseFromOffice |
P163573
|
FINISHED |
| Object | Han chancellor’s family |
—
|
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: Han chancellor’s family | Statement: [House of Cao, roseFromOffice, Han chancellor’s family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roseFromOffice Context triple: [House of Cao, roseFromOffice, Han chancellor’s family]
-
A.
roseToProminenceUnder
Indicates that an entity became well-known, influential, or successful during the period of another entity’s leadership, guidance, or dominance.
-
B.
officeAfter
Indicates that one office or term of office occurs chronologically after another office or term.
-
C.
officeStart
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
-
D.
roseToProminenceIn
Indicates the time or context in which an entity became widely recognized, influential, or notable.
-
E.
officeStartFor
Indicates the time or date at which an entity begins its term, role, or period of service in an office or official position.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b0218808190b3e543cc1a0bb5cb |
completed | May 2, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 7:30 p.m.