Triple
T30365682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gangte |
E772414
|
entity |
| Predicate | isSpokenInIndianState |
P31689
|
FINISHED |
| Object | Manipur |
—
|
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: Manipur | Statement: [Gangte, isSpokenInIndianState, Manipur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokenInIndianState Context triple: [Gangte, isSpokenInIndianState, Manipur]
-
A.
spokenInIndianState
chosen
Indicates that a language is spoken within the geographical boundaries of a specific Indian state.
-
B.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
-
C.
includesIndianStateOrTerritory
Indicates that one entity encompasses, contains, or covers the area of an Indian state or union territory.
-
D.
usedInIndianStates
Indicates that something is utilized or applied within one or more states of India.
-
E.
partlyLocatedInIndianState
Indicates that an entity is geographically or administratively situated such that only part of it lies within the boundaries of a specified Indian state.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6827fabc88190a34dffaa5c83e1f1 |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:58 p.m.