Triple
T27246339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singalila Ridge |
E687353
|
entity |
| Predicate | borderTownAccess |
P189421
|
FINISHED |
| Object | Manebhanjan |
—
|
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: Manebhanjan | Statement: [Singalila Ridge, borderTownAccess, Manebhanjan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTownAccess Context triple: [Singalila Ridge, borderTownAccess, Manebhanjan]
-
A.
borderTownAcrossBorder
Indicates that a town lies on one side of a border directly opposite or adjacent to a town on the other side of that border.
-
B.
borderPass
Indicates that one entity crosses or moves through the boundary separating two regions or jurisdictions.
-
C.
borderCityStatus
Indicates that a city holds a designated status due to its location on or near a political or geographic border.
-
D.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
E.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
- F. None of above. chosen
Provenance (4 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 27, 2026, 10:41 a.m.