Triple
T30002020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shingon Ritsu school |
E762193
|
entity |
| Predicate | monasticOrientation |
P12141
|
FINISHED |
| Object | strong |
—
|
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: strong | Statement: [Shingon Ritsu school, monasticOrientation, strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticOrientation Context triple: [Shingon Ritsu school, monasticOrientation, strong]
-
A.
monasticTradition
chosen
Indicates that an entity follows, belongs to, or is characterized by a particular monastic rule, lineage, or way of religious life.
-
B.
monasticLife
Indicates a relationship where an entity lives according to monastic rules, practices, and commitments, typically within a religious community.
-
C.
roleInMonasticism
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
-
D.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
-
E.
monasteryOrder
Indicates that a monastery belongs to, follows, or is affiliated with a particular religious order.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794eecb48190a679439c69a17137 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:41 p.m.