Triple
T25397223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Railways of India |
E636324
|
entity |
| Predicate | locatedInTerrain |
P103580
|
FINISHED |
| Object | hill regions of India |
—
|
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: hill regions of India | Statement: [Mountain Railways of India, locatedInTerrain, hill regions of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTerrain Context triple: [Mountain Railways of India, locatedInTerrain, hill regions of India]
-
A.
locatedOnTerrain
Indicates that one entity is physically situated on or atop a particular terrain surface.
-
B.
involvesTerrain
chosen
Indicates that the relationship or action takes place in, across, or is directly affected by a specified type of terrain or landform.
-
C.
hasTerrainFor
Indicates that a location or area possesses terrain suitable or designated for a particular use, activity, or feature.
-
D.
locatedAboveGround
Indicates that one entity is positioned at a level higher than the ground surface, not buried or below ground.
-
E.
hasTerrainCharacter
Indicates that one entity possesses or exhibits a particular terrain-related feature or characteristic in relation to 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 21, 2026, 1:50 p.m.