Triple
T38499822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legislative Council (India) |
E919795
|
entity |
| Predicate | currentStatesWithCouncil |
P201287
|
FINISHED |
| Object | Andhra Pradesh |
—
|
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: Andhra Pradesh | Statement: [Legislative Council (India), currentStatesWithCouncil, Andhra Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentStatesWithCouncil Context triple: [Legislative Council (India), currentStatesWithCouncil, Andhra Pradesh]
-
A.
numberOfRegionalCouncils
Indicates the total count of regional councils associated with a given entity.
-
B.
viewOfCouncils
Indicates that one entity holds a particular perspective, opinion, or stance regarding councils or council-related matters.
-
C.
hasCouncilChambers
Indicates that an entity possesses or contains designated rooms or facilities used for council meetings or deliberations.
-
D.
councilSets
Indicates that a council establishes, determines, or formally decides a rule, policy, standard, or other governing parameter.
-
E.
hasCouncilStructure
Indicates that an entity is organized or governed according to a specific council-based structure or system.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69ffe6130698819099328fce92bb2784 |
completed | May 10, 2026, 1:57 a.m. |
Created at: May 3, 2026, 4:31 p.m.