Triple
T20566881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reflections on Things at Hand |
E504987
|
entity |
| Predicate | hasTraditionalChineseTitle |
P6282
|
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: [Reflections on Things at Hand, hasTraditionalChineseTitle, 近思錄]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalChineseTitle Context triple: [Reflections on Things at Hand, hasTraditionalChineseTitle, 近思錄]
-
A.
hasChineseTitle
Indicates that an entity possesses a title or name expressed in the Chinese language.
-
B.
hasTitleInRevisedRomanization
Indicates that an entity has a specific title expressed using the Revised Romanization system for Korean.
-
C.
hasTraditionalCharacter
Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
-
D.
ChineseNameTraditional
chosen
Indicates that an entity’s name is given in traditional Chinese characters.
-
E.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a33f7c8190966da03528dfe8aa |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.