Triple
T33526103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 周公 |
E858643
|
entity |
| Predicate | 摄政对象 |
P6997
|
FINISHED |
| Object | 周成王 |
—
|
NE NERFINISHED |
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: 周成王 | Statement: [周公, 摄政对象, 周成王]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 摄政对象 Context triple: [周公, 摄政对象, 周成王]
-
A.
regentFor
chosen
Indicates that one entity serves as the ruling authority on behalf of another, typically during the latter’s minority, absence, or incapacity.
-
B.
regentOf
Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
-
C.
correspondsToReignTitleHolder
Indicates that a given reign or period of rule is associated with, and held by, a specific title holder.
-
D.
regent
Indicates that one entity serves as the regent, exercising ruling authority on behalf of another (typically a monarch or state), usually during a period when the rightful ruler is unable to govern.
-
E.
reignAsHeirApparentEnd
Indicates the point in time or event at which an individual’s period of serving as heir apparent to a throne or title comes to an end.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.