Triple
T30609569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuzu Nembutsu |
E779138
|
entity |
| Predicate | meritConcept |
P69507
|
FINISHED |
| Object | transfer of merit |
—
|
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: transfer of merit | Statement: [Yuzu Nembutsu, meritConcept, transfer of merit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meritConcept Context triple: [Yuzu Nembutsu, meritConcept, transfer of merit]
-
A.
encouragedMeritocracy
Indicates that an entity promoted or supported a system in which individuals advance based on ability or merit rather than other factors.
-
B.
rankConcept
Indicates that one concept is ordered or prioritized relative to other concepts according to some ranking criterion.
-
C.
recognizedCriterion
Indicates that something is acknowledged or accepted as a valid standard, measure, or basis for judgment in a given context.
-
D.
mustAchieve
Indicates that an entity is required or obligated to attain or accomplish a specified goal, condition, or outcome.
-
E.
dedicatedToConcept
chosen
Indicates that something is specifically devoted, committed, or purposefully directed toward a particular concept or abstract idea.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689b87220819084859503a4458c0d |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.