Triple
T31265397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tedim |
E797238
|
entity |
| Predicate | hasNearbyIndianState |
P85007
|
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: [Tedim, hasNearbyIndianState, Manipur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyIndianState Context triple: [Tedim, hasNearbyIndianState, Manipur]
-
A.
includesIndianStateOrTerritory
Indicates that one entity encompasses, contains, or covers the area of an Indian state or union territory.
-
B.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
-
C.
isPartOfIndianState
Indicates that one entity is a constituent part or subdivision of an Indian state.
-
D.
hasNeighbouringState
Indicates that one state shares a common border or is directly adjacent geographically to another state.
-
E.
borderingIndianStates
chosen
Indicates that one or more Indian states share a common land or maritime boundary with a given geographic or political entity.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: April 29, 2026, 9:12 p.m.