Triple
T37770956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zen |
E941544
|
entity |
| Predicate | JapaneseNameOf |
P28734
|
FINISHED |
| Object | Chan Buddhism |
—
|
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: Chan Buddhism | Statement: [Zen, JapaneseNameOf, Chan Buddhism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JapaneseNameOf Context triple: [Zen, JapaneseNameOf, Chan Buddhism]
-
A.
nameInJapaneseKana
Indicates that an entity’s name is written or represented using Japanese kana characters.
-
B.
JapaneseNameOrigin
Indicates that one entity’s name originates from or is derived from the Japanese language or naming tradition in relation to another entity.
-
C.
formerJapaneseNameOf
Indicates that one entity was previously used as the Japanese name for another entity but is no longer its current Japanese name.
-
D.
hasNameInJapanese
chosen
Indicates that an entity is associated with a specific name expressed in the Japanese language.
-
E.
JapaneseNameReading
Indicates that one entity is the reading or pronunciation (e.g., in kana or romaji) of a Japanese name represented by the other 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbaf1d1db481909df74c152c53ec10 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.