Triple
T37913409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guifeng Zongmi |
E945746
|
entity |
| Predicate | honorificNameMeaning |
P167770
|
FINISHED |
| Object | Turtle Peak |
—
|
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: Turtle Peak | Statement: [Guifeng Zongmi, honorificNameMeaning, Turtle Peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificNameMeaning Context triple: [Guifeng Zongmi, honorificNameMeaning, Turtle Peak]
-
A.
honorificMeaningOfName
chosen
Indicates that a name carries an honorific or respectful meaning associated with a person or entity.
-
B.
honorificSuffixMeaning
Indicates that a particular honorific suffix conveys a specific meaning or nuance in how someone is addressed.
-
C.
honorificNameOf
Indicates that one entity is the honorific or respectful name or title used to refer to another entity.
-
D.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
E.
honorificMeaningApproximate
Indicates that one entity’s honorific expression conveys an approximate or loosely equivalent respectful meaning to another honorific form.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:20 p.m.