Triple
T25987453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dispur |
E646240
|
entity |
| Predicate | seatOfLegislativeAssemblyOf |
P112738
|
FINISHED |
| Object | Assam |
—
|
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: Assam | Statement: [Dispur, seatOfLegislativeAssemblyOf, Assam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatOfLegislativeAssemblyOf Context triple: [Dispur, seatOfLegislativeAssemblyOf, Assam]
-
A.
seatOfAssembly
chosen
Indicates that a location serves as the official meeting place or headquarters of a legislative or deliberative assembly.
-
B.
haveLegislativeAssemblyIn
Indicates that an entity possesses or is associated with a legislative assembly located in a specified place.
-
C.
legislativeAssemblyConstituency
Indicates that one entity is a legislative assembly constituency associated with or represented by another entity (such as a place, jurisdiction, or legislative body).
-
D.
legislativeAssemblySeats
Indicates the number of seats an entity holds or is allocated in a legislative assembly.
-
E.
seatOfRepresentative
Indicates the location or institution where a representative officially holds their position or exercises their duties.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605446ca48190907baef523f13ccf |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:55 a.m.