Triple
T28374310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 成湯 |
E718714
|
entity |
| Predicate | 歷史評價 |
P675
|
FINISHED |
| Object | 以德伐暴的典範 |
—
|
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: 以德伐暴的典範 | Statement: [成湯, 歷史評價, 以德伐暴的典範]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 歷史評價 Context triple: [成湯, 歷史評價, 以德伐暴的典範]
-
A.
historicalAssessment
chosen
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
-
B.
inHistoriography
Indicates a relationship where something is discussed, interpreted, or treated within the field or discourse of historiography.
-
C.
歴史
Indicates a relationship where something pertains to, records, or is involved in the events, development, or study of the past over time.
-
D.
characterizationByHistorians
Indicates how historians have described, interpreted, or evaluated a person, event, or phenomenon in their scholarly work.
-
E.
historicalDiscipline
Indicates that one entity is a field or branch of academic study within the broader domain of history in relation to another entity.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c5d1290819087cbb832239699d4 |
completed | May 2, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:02 a.m.