Triple
T26587114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haflong constituency |
E667238
|
entity |
| Predicate | borderingAreasInclude |
P57389
|
FINISHED |
| Object | hilly tracts around Haflong |
—
|
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: hilly tracts around Haflong | Statement: [Haflong constituency, borderingAreasInclude, hilly tracts around Haflong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingAreasInclude Context triple: [Haflong constituency, borderingAreasInclude, hilly tracts around Haflong]
-
A.
borderRegionsInclude
chosen
Indicates that the specified border area encompasses or contains the referenced regions within its boundaries.
-
B.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
C.
boundaryMayInclude
Indicates that the boundary of one entity can optionally contain or encompass another entity.
-
D.
hasCrossBorderArea
Indicates that an entity is associated with or spans a geographic area that extends across national or jurisdictional borders.
-
E.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
- 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_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 27, 2026, 2:06 a.m.