Triple
T14997453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Dismas |
E373993
|
entity |
| Predicate | nameInEasternTradition |
P66059
|
FINISHED |
| Object | Rakh (various forms) |
—
|
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: Rakh (various forms) | Statement: [Saint Dismas, nameInEasternTradition, Rakh (various forms)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInEasternTradition Context triple: [Saint Dismas, nameInEasternTradition, Rakh (various forms)]
-
A.
nameInChinese
Indicates that an entity has a specific written name or label expressed in the Chinese language.
-
B.
nameInMcCuneReischauer
Indicates that an entity’s name is represented using the McCune–Reischauer romanization system.
-
C.
ChineseNameTraditional
Indicates that an entity’s name is given in traditional Chinese characters.
-
D.
hasEasternName
chosen
Indicates that an entity is associated with or known by a name used in an Eastern language or cultural context.
-
E.
pairedTraditionalName
Indicates that two entities are associated as a traditional name pair, typically used together or in customary combination within a cultural or naming convention.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded718e4288190b5e144f82299a194 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.