Triple
T4512917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gautama |
E102090
|
entity |
| Predicate | roleInNyaya |
P57099
|
FINISHED |
| Object | foundational authority |
—
|
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: foundational authority | Statement: [Gautama, roleInNyaya, foundational authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInNyaya Context triple: [Gautama, roleInNyaya, foundational authority]
-
A.
legalCaseRole
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
-
B.
legalSystemRole
Indicates the specific function, capacity, or position an entity holds within a legal or judicial system.
-
C.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
-
D.
judicialRole
Indicates that one entity holds or performs a specific official function or position within the judicial system in relation to another entity or legal matter.
-
E.
courtRole
Indicates the specific capacity or position an entity holds within a court proceeding or judicial context.
- F. None of above. chosen
Provenance (4 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5722d8fc81909c5f2d9a38d17a6b |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:02 p.m.