Triple
T859928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vedic period |
E18575
|
entity |
| Predicate | politicalInstitution |
P12532
|
FINISHED |
| Object | sabha |
—
|
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: sabha | Statement: [Vedic period, politicalInstitution, sabha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalInstitution Context triple: [Vedic period, politicalInstitution, sabha]
-
A.
politicalForm
Indicates the type or structure of governance or political organization that characterizes an entity.
-
B.
politicalOrganization
Indicates that an entity is a political organization, such as a party, movement, or group engaged in political activities or governance-related objectives.
-
C.
politicalEntity
Indicates that an entity functions as or is recognized as a political unit, organization, or actor within a political system.
-
D.
parliamentaryHouse
chosen
Indicates that one entity functions as a parliamentary chamber or house within the legislative system of another entity.
-
E.
representedPoliticalEntity
Indicates that one entity has served as an official political representative or agent acting on behalf of another political entity.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac50e5ec81908ac0c4b7123b4ebb |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.