Triple
T32108549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algapur |
E820052
|
entity |
| Predicate | hasLegislatureCountry |
P176290
|
FINISHED |
| Object | Parliament of India |
—
|
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: Parliament of India | Statement: [Algapur, hasLegislatureCountry, Parliament of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegislatureCountry Context triple: [Algapur, hasLegislatureCountry, Parliament of India]
-
A.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
B.
hasLegislatureName
chosen
Indicates the formal name assigned to a legislature associated with an entity.
-
C.
legislativeArea
Indicates the geographic or jurisdictional area over which a legislative body or legislative activity has authority or relevance.
-
D.
hasLegislativeState
Indicates that an entity is associated with, governed by, or falls under the jurisdiction of a particular legislative state or lawmaking authority.
-
E.
legislativeBodyOf
Indicates that one entity is the official legislative body (lawmaking assembly) of another entity, typically a political unit such as a country, state, or city.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 1, 2026, 12:27 a.m.