Triple
T37733175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahasamghika |
E940214
|
entity |
| Predicate | hadSubsect |
P17297
|
FINISHED |
| Object | Lokottaravāda |
—
|
NE NERFINISHED |
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: Lokottaravāda | Statement: [Mahasamghika, hadSubsect, Lokottaravāda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSubsect Context triple: [Mahasamghika, hadSubsect, Lokottaravāda]
-
A.
hadSubtypes
Indicates that an entity served as a broader category or type that included one or more more specific subtypes.
-
B.
hadSubcommittee
Indicates that an entity (typically an organization or committee) possessed or was associated with a subordinate committee or subcommittee.
-
C.
hasSubchron
Indicates that a given chronostratigraphic unit is divided into, or contains, one or more subordinate subchrons.
-
D.
majorSubsect
Indicates that one group, movement, or tradition is a principal or primary subdivision within a larger religious, ideological, or organizational entity.
-
E.
hasSect
chosen
Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.