Triple
T25441255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barak Valley cultural identity |
E637512
|
entity |
| Predicate | hasKeyCityContext |
P25162
|
FINISHED |
| Object | Silchar |
—
|
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: Silchar | Statement: [Barak Valley cultural identity, hasKeyCityContext, Silchar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyCityContext Context triple: [Barak Valley cultural identity, hasKeyCityContext, Silchar]
-
A.
hasComponentCity
Indicates that an entity includes or is composed of one or more cities as its constituent parts.
-
B.
hasAssociatedCity
chosen
Indicates that one entity is linked or related to a specific city, typically as its location, base, or primary area of association.
-
C.
hasCityPlanningContext
Indicates that something is associated with, relevant to, or situated within a particular city planning context, such as urban development, zoning, or land-use planning.
-
D.
hasTargetCity
Indicates that something is directed toward, intended for, or specifically associated with a particular city as its target.
-
E.
hasCityStatusFor
Indicates that an entity holds official city status within the jurisdiction or context of another 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 2 p.m.