Triple
T27385411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satō Norikiyo |
E691356
|
entity |
| Predicate | tookMonasticVowsIn |
P40813
|
FINISHED |
| Object | around 1140 |
—
|
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: around 1140 | Statement: [Satō Norikiyo, tookMonasticVowsIn, around 1140]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookMonasticVowsIn Context triple: [Satō Norikiyo, tookMonasticVowsIn, around 1140]
-
A.
tookReligiousVows
chosen
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
B.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
C.
vowedCelibacyWith
Indicates a mutual commitment between entities to abstain from sexual or romantic relationships, typically formalized as a shared vow of celibacy.
-
D.
forcedIntoMonasticLifeBy
Indicates that one entity compelled another, against their will or under strong pressure, to enter and live a monastic or religious life.
-
E.
takesVowsOf
Indicates that an entity formally commits to specific vows, promises, or oaths, typically within a religious, ceremonial, or institutional 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62c8af8508190bf5e40515d5d8f34 |
completed | May 2, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:24 p.m.