Triple
T34940303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 王屋山 |
E1007696
|
entity |
| Predicate | 在典故中角色 |
P42552
|
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.
roleInShinKokinWakashu
Indicates the specific role or involvement an entity has in relation to the Shin Kokin Wakashū (e.g., as compiler, editor, or contributor).
-
B.
threeKingdomsContext
Indicates that the relationship or action is situated within, or specifically relevant to, the historical and narrative context of the Three Kingdoms period.
-
C.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
-
D.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
E.
地域的役割
Indicates that something has a specific function, responsibility, or role within a particular region or locality.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.