Triple
T28374264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 商汤 |
E718713
|
entity |
| Predicate | 文化形象 |
P27550
|
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.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
-
B.
culturalIdentifier
Indicates that one entity serves as a marker, label, or attribute that identifies or characterizes the cultural affiliation, background, or context of another entity.
-
C.
hasCulturalIcon
chosen
Indicates that an entity is associated with or possesses a person, symbol, or object widely recognized as a significant representation of a particular culture.
-
D.
culturalElements
Indicates a relationship where certain elements (such as practices, symbols, or artifacts) belong to, express, or characterize a particular culture or cultural context.
-
E.
culturalSphere
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by 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.