Triple
T38259859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riprap and Cold Mountain Poems |
E1017898
|
entity |
| Predicate | translationsOf |
P52481
|
FINISHED |
| Object | Han Shan |
—
|
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: Han Shan | Statement: [Riprap and Cold Mountain Poems, translationsOf, Han Shan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translationsOf Context triple: [Riprap and Cold Mountain Poems, translationsOf, Han Shan]
-
A.
languageOfTranslations
Indicates that one entity is the language into which another entity (such as a text or work) has been translated.
-
B.
translatedIn
Indicates that a work, text, or content has been rendered from its original language into another specified language or linguistic form.
-
C.
translationOn
chosen
Indicates that one entity is a translation of another entity, typically expressing the same content in a different language or linguistic form.
-
D.
requestedTranslationOf
Indicates that one entity has asked for another entity to be translated into a different language or form.
-
E.
translationProperty
Indicates a relationship where one entity serves as a translated counterpart or translation-specific attribute of 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:30 p.m.