Triple
T26587115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haflong constituency |
E667238
|
entity |
| Predicate | isSeatFor |
P77969
|
FINISHED |
| Object | Member of Legislative Assembly of Assam |
—
|
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: Member of Legislative Assembly of Assam | Statement: [Haflong constituency, isSeatFor, Member of Legislative Assembly of Assam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeatFor Context triple: [Haflong constituency, isSeatFor, Member of Legislative Assembly of Assam]
-
A.
seatIs
chosen
Indicates that one entity functions as the seat or seating position of another entity.
-
B.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
-
C.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
D.
isSeatWithin
Indicates that one seat is located inside the spatial bounds or interior area defined by another object or region.
-
E.
isSafeSeatFor
Indicates that one entity is a suitable and secure seating option for another entity, posing no unacceptable risk or harm.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f615229fb481909b7fe7d9d17b8604 |
completed | May 2, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:06 a.m.