Triple
T28374311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 成湯 |
E718714
|
entity |
| Predicate | 相關典故 |
P79971
|
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.
関連事件
Indicates a relationship where one event is connected or related to another event, typically as part of the same case, incident, or context.
-
B.
関連主題
Indicates that there exists a thematically or contextually related subject connected to the given entity.
-
C.
開基
Indicates the act of founding or establishing something for the first time, such as initiating a lineage, enterprise, or domain.
-
D.
関連城郭
Indicates a relationship where something is associated with or related to a particular castle or fortification.
-
E.
associatedWithAnecdote
chosen
Indicates a relationship where something is linked or connected to a particular anecdote, such as being based on, derived from, or exemplified by that anecdotal account.
- 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.