Triple
T37913311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dazhi |
E945743
|
entity |
| Predicate | appliedAsTitle |
P10405
|
FINISHED |
| Object | Chan master |
—
|
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: Chan master | Statement: [Dazhi, appliedAsTitle, Chan master]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedAsTitle Context triple: [Dazhi, appliedAsTitle, Chan master]
-
A.
appliedToTitle
Indicates that something (such as a rule, action, or attribute) is applied specifically to a given title.
-
B.
usesTitleIn
Indicates that an entity is referred to using a particular title within a specified context or medium.
-
C.
usesTitle
chosen
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
D.
appliedToTitleHolder
Indicates that an action, rule, or condition is directed specifically toward the current holder of a particular title or position.
-
E.
usedAsTitleFrom
Indicates that something functions as a title derived from or originating from another source or context.
- 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_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 3, 2026, 4:20 p.m.