Triple
T34020398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mula Sangh |
E872364
|
entity |
| Predicate | hasSubLineages |
P196076
|
FINISHED |
| Object | regional Digambara monastic branches |
—
|
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: regional Digambara monastic branches | Statement: [Mula Sangh, hasSubLineages, regional Digambara monastic branches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubLineages Context triple: [Mula Sangh, hasSubLineages, regional Digambara monastic branches]
-
A.
containsLineages
chosen
Indicates that one entity includes or encompasses one or more specified lineages within its scope or structure.
-
B.
hasLineageStructure
Indicates that an entity participates in or exhibits a hierarchical ancestry or lineage-based structural relationship to other entities.
-
C.
hasLineageMember
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
-
D.
hasLineageCharacteristic
Indicates that an entity possesses a specific trait, feature, or quality that is inherited or derived from its lineage or ancestral line.
-
E.
hasSubtaxon
Indicates that one taxonomic group is a subordinate or included taxon within another taxonomic group.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 1, 2026, 1:51 a.m.