Triple
T11672837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hongren |
E277421
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 弘忍 |
E277421
|
NE 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: [Hongren, nativeName, 弘忍]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 弘忍 Context triple: [Hongren, nativeName, 弘忍]
-
A.
行基
行基 was a prominent Japanese Buddhist monk of the Nara period known for his extensive public works and for helping popularize Buddhism among common people.
-
B.
智忠
智忠 is a Chinese given name composed of the characters for "wisdom" (智) and "loyalty" (忠), commonly used for males.
-
C.
Huineng
Huineng was the influential Sixth Patriarch of Chan (Zen) Buddhism in China, renowned for his teachings on sudden enlightenment and non-dual awareness.
-
D.
Shenxiu
Shenxiu was a prominent early Chan (Zen) Buddhist monk of the 7th century, known as a leading figure of the so-called Northern School and a key rival to Huineng in later Chan tradition.
-
E.
Hongren
chosen
Hongren was a seminal early patriarch of Chan (Zen) Buddhism in China, renowned for shaping its meditative teachings and transmission.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a443b6848190a1eb6825fbc49d08 |
completed | April 10, 2026, 7:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef13e1b3d8819085ea806280ed69d3 |
completed | April 27, 2026, 7:44 a.m. |
Created at: April 8, 2026, 9:40 p.m.