Triple
T35161985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalandhar Cantt railway station |
E1015290
|
entity |
| Predicate | connectsRegionally |
P112692
|
FINISHED |
| Object | Punjab |
—
|
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: Punjab | Statement: [Jalandhar Cantt railway station, connectsRegionally, Punjab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsRegionally Context triple: [Jalandhar Cantt railway station, connectsRegionally, Punjab]
-
A.
connectsRegionalCity
Indicates a relationship where one entity serves as a link or transport route between a regional city and another location.
-
B.
connectsCountryOrRegion
Indicates that one entity establishes a connection, link, or association to a specific country or region.
-
C.
connectsProvinceOrRegion
chosen
Indicates that one entity serves to link or provide a connection between a specific province or region and another entity.
-
D.
connectsRegions
Indicates a relationship where one entity links or joins two or more distinct regions, enabling passage, interaction, or continuity between them.
-
E.
coordinatesRegionally
Indicates that an entity organizes, aligns, or manages activities or operations across multiple areas within a specific geographic region.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:02 p.m.